cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: SAXParseException - who's to blame?
Date Thu, 12 Feb 2009 16:01:53 GMT

Two thoughts:

1)  Any chance you could use something like wireshark to get the raw byte 
streams?   We had one other report a month or two ago about extra bytes at the 
end of the message, but no-one could ever reproduce it and the thought was 
that the proxy server in the middle or some other wrapper was adding it.   

2) You could also try turning off http chunking.   Some older servers don't 
properly support it.   Maybe the "0" at the end to mark the end of the chunk 
is pushing through to the parser or something.


On Wed February 11 2009 7:19:04 pm buzzterrier wrote:
> I am getting the following error when sending a soap request to a remote
> service and I am not quite sure who is throwing it. I found that this is
> sometimes thrown when some elements had text containing unescaped extended
> characters. But I have some posts that are failing and I cannot see
> anything wrong with the package. I am kind of new to SOAP so I am not sure
> if CXF is causing this error, or if the server that is consuming the SOAP
> message is.
> Here is an fault message:
> <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope
> xmlns:soapenv=""
> xmlns:xsd=""
> xmlns:xsi=""><soapenv:Body><soapen
>xml.sax.SAXParseException: Content is not allowed in trailing
> section.</faultstring><detail><ns1:hostname
> xmlns:ns1="">sb-partners-java002.svale.netledger
> Should I go harp on the service provider? Does anyone have any idea what
> else might cause that message?
> -----
> Buzzterrier
> View my blog: Ordinary Average
> Developer...

Daniel Kulp

View raw message