[ http://issues.apache.org/jira/browse/AXIS2-1345?page=all ]
Davanum Srinivas resolved AXIS2-1345.
-------------------------------------
Resolution: Fixed
Already fixed the axis2.xml that gets into the war.
-- dims
> HTTP/BOM content before SOAP response from 1.1-RC services
> ----------------------------------------------------------
>
> Key: AXIS2-1345
> URL: http://issues.apache.org/jira/browse/AXIS2-1345
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: core
> Affects Versions: 1.1
> Environment: Tomcat 5.0 + Axis2 1.1 RC on server side. SOAP client
> based on HttpURLConnection on client side.
> Reporter: Dan Jemiolo
>
> (reposted from axis-dev)
> I'm having a problem with the Axis2 1.1 RC on the client side. My services
> still work as normal when I upgrade them to 1.1, but my non-Axis2 clients
> fail when trying to parse the response message. I get the following error
> message from the JAXP DocumentBuilder (Xerces):
> [Fatal Error] :1:1: Content is not allowed in prolog.
> I initially thought this was related to an old bug in the processing of
> byte-order marks at the beginning of XML documents:
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4508058
> However, when I look at the SOAP response in my TCP/IP monitor, I see the
> following:
> --MIMEBoundaryurn_uuid_D29F76E66EC97F738911605255931147
> content-type: application/xop+xml; charset=UTF-8;
> type="application/soap+xml";
> content-transfer-encoding: binary
> content-id: <0.urn:uuid:[EMAIL PROTECTED]>
> <?xml version='1.0' encoding='UTF-8'?>
> <soapenv:Envelope xmlns:wsa="http://www.w3.org/2005/08/addressing";
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
> <soapenv:Header>
> <wsa:To>http://www.w3.org/2005/08/addressing/anonymous</wsa:To>
> <wsa:ReplyTo><wsa:Address>http://www.w3.org/2005/08/addressing/none</wsa:Address></wsa:ReplyTo>
> <wsa:MessageID>urn:uuid:26F070AB96AC17B8D811605255931048</wsa:MessageID>
> <wsa:Action>http://ws.apache.org/muse/test/http-server/Stop</wsa:Action>
> <wsa:RelatesTo
> wsa:RelationshipType="http://www.w3.org/2005/08/addressing/reply";>uuid:80882292-b452-7e92-919d-01ed1f001f17</wsa:RelatesTo>
> </soapenv:Header>
> <soapenv:Body>
> <muse-op:StopResponse xmlns:tns="http://ws.apache.org/axis2";
> xmlns:muse-op="http://ws.apache.org/muse/test/http-server"; />
> </soapenv:Body>
> </soapenv:Envelope>
> --MIMEBoundaryurn_uuid_D29F76E66EC97F738911605255931147--
> Can anyone comment on why the MIMEBoundary wrapper and some HTTP headers seem
> to be in the POST data? I think this is what's causing Xerces to fail when
> parsing the POST content into a DOM Document. This may be a significant issue
> since most web services clients assume that the only POST data in a SOAP
> response is the SOAP XML document.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
