All,
I am trying to find out what triggers the generation of the MIME boundary in the SOAP/HTTP. Apparently I'm having issues with the MIME boundary being present in the message? Apparently an integrating application thinks that the content-type needs to be application/xop+xml. I would appreciate if you have any suggestions/ideas. Thanks Sumit Sample Message HTTP/1.1 200 OK Cache-Control: no-cache="Set-Cookie" Connection: close Date: Wed, 15 Jul 2009 14:51:22 GMT Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_B32334D9163F7E5E771247669489559; type="application/soap+xml"; start="<0.urn:uuid:b32334d9163f7e5e771247669489...@apache.org>"; action="urn:reviewResponse" Set-Cookie: JSESSIONID=2hdGKdsKlDvVZyLDfY69d7R3GxTh1gLQxp1124l1nPLsn5j1ynRq!15167569 95; path=/ X-Powered-By: Servlet/2.5 JSP/2.1 --MIMEBoundaryurn_uuid_B32334D9163F7E5E771247669489559 Content-Type: application/soap+xml; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-ID: <0.urn:uuid:b32334d9163f7e5e771247669489...@apache.org> <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><soapenv:Body><SOM E RESPONSE ></soapenv:Body></soapenv:Envelope> --MIMEBoundaryurn_uuid_B32334D9163F7E5E771247669489559--
