axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "keith chapman" <>
Subject Re: SOAP Envelope not serializable for robust-in-only operations
Date Wed, 17 Sep 2008 12:02:24 GMT
What is the mechanism you used to access the SOAPEnvelop from the service
implementation class?


On Wed, Sep 17, 2008 at 4:58 PM, Martin Scholl <> wrote:

> Hi,
> I got some trouble with the SOAP Envelope contained in the MessageContext
> of in-only operations, which I access in the ServiceSkeleton implementation
> class. When calling toString operation on any element of the envelope (body,
> header, etc.) or on the envelope itself I receive an OMException, caused by
> a NoSuchElementException. When calling toString operation on the envelope
> which was converted in a org.w3c.dom.Element before I receive a
> RuntimeException with message 'Can not serialize OM Element Envelope'. This
> exception is caused by a XMLStreamException.
> We use XMLBeans databinding which does not complain about anything and
> works well. Additionally in-out operations' SOAP Envelope is valid. I could
> not manage to find any clue yet. We use Axis2 1.3 on top of Tomcat6 and
> generate the service client and server classes from WSDL 1.1 using WSDL2Java
> and XMLBeans 2.2.0.
> Any ideas?
> Thanks in advance.
> Regards,
> Martin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.


View raw message