Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Urgent
-
Resolution: Won't Fix
-
Affects Version/s: XDRSRCSimulator-1.0-GA
-
Fix Version/s: XDRSRCSimulator-1.2-SR1
-
Labels:None
Description
messages sent by the XDR source are expected to be MIME multipart messages.
by now, the XML and PDF documents are embedded in the SOAP message, this does not match the SOAP requirements and some systems can not extract the information from the received message.
HTTP header of a MIME multipart must look like something like that:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_7451DCA4DAD2ADC2761289828495785; type="application/xop+xml"; start="0.urn:uuid:7451DCA4DAD2ADC2761289828495786@apache.org"; start-info="application/soap+xml"; action="urn:ihe:iti:2007:CrossGatewayRetrieveResponse"
Transfer-Encoding: chunked
Date: Mon, 15 Nov 2010 13:41:33 GMT
And the SOAP message must contain references to the other parts of the multipart MIME by using the xop:Include element and a Content-ID for each part
by now, the XML and PDF documents are embedded in the SOAP message, this does not match the SOAP requirements and some systems can not extract the information from the received message.
HTTP header of a MIME multipart must look like something like that:
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_7451DCA4DAD2ADC2761289828495785; type="application/xop+xml"; start="0.urn:uuid:7451DCA4DAD2ADC2761289828495786@apache.org"; start-info="application/soap+xml"; action="urn:ihe:iti:2007:CrossGatewayRetrieveResponse"
Transfer-Encoding: chunked
Date: Mon, 15 Nov 2010 13:41:33 GMT
And the SOAP message must contain references to the other parts of the multipart MIME by using the xop:Include element and a Content-ID for each part
