axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Jemiolo <>
Subject [Axis2][RC-1.1] problem with HTTP/BOM content before SOAP response
Date Wed, 11 Oct 2006 00:32:39 GMT

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:

However, when I look at the SOAP response in my TCP/IP monitor, I see the 

content-type: application/xop+xml; charset=UTF-8; 
content-transfer-encoding: binary
content-id: <>

<?xml version='1.0' encoding='UTF-8'?>
<soapenv:Envelope xmlns:wsa="" 
<muse-op:StopResponse xmlns:tns="" 
xmlns:muse-op="" />

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.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message