This is by design. To avoid the overhead of building a complete DOM
like representation of the message, Axis2 actually consumes the
message (more specifically the content of the SOAP Body element) when
converting it to a Java object. Once that is done, the original
message can no longer be serializ
From: Sterpu Victor
Sent: Wednesday, November 2, 2016 11:57 AM
To: Martin Gainty; java-user@axis.apache.org
Subject: Re[2]: Raw SOAP XML response
It didn't work.
This is what I did: I deleted from the directory of Axis2\lib 4 files:
axiom-jaxb-1.2.19.jar, axiom-
It didn't work.
This is what I did: I deleted from the directory of Axis2\lib 4 files:
axiom-jaxb-1.2.19.jar, axiom-api-1.2.19.jar, axiom-dom-1.2.19.jar,
axiom-impl-1.2.19.jar
and I added these 4 files:
axiom-api-1.2.20.jar,axiom-dom-1.2.20.jar,axiom-impl-1.2.20.jar,axiom-jaxb-1.2.20.jar.
I use
possible outdated version of axiom
* In Axiom versions prior to 1.2.9, the sequence of events was
inconsistent if the
* underlying stream is XOP encoded and caching is disabled (see
WSCOMMONS-485).
* This made it necessary for the caller to (partially) handle the XOP
processing
Hello
I need to save the raw SOAP XML response from Axis2(I use axis 2 1.7.3).
When Axis2 call retusrns an error this code works: String response =
sc.getLastOperationContext().getMessageContext("In").getEnvelope().toString();
But when I run a succesful Axis2 call the same code gives the followi
