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 serialized. In the fault case the situation
is different because Axis2 doesn't get to the point where it would
consume (part of) the message.
Andreas
On Wed, Nov 2, 2016 at 1:37 PM, Sterpu Victor <vic...@caido.ro> wrote:
> 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 following
> error: "java.lang.IllegalStateException: Can't process next node because
> caching is disabled"
>
> I tryed to enable cache like this, but it didn't work:
>
> ServiceClient sc =
> (ServiceClient)method_getServiceClient.invoke(objectReflect);
> ServiceContext srv_context =
> sc.getServiceContext();
>
> srv_context.setCachingOperationContext(true);
> OperationContext oc= new OperationContext();
> oc.setComplete(true);
> srv_context.setLastOperationContext(oc);
>
> Thank you
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org
