It may be a bug that it doesn't give the full envelope - someone else
may be able to comment and if not file a jira. However, the handler
approach can work as the SOAPMonitor uses
messageContext.getEnvelope().toString() . Look at the soapmonitor mar
and SOAPMonitorHandler.java - the soapmonitor displays both the
response and request correctly with 1.1 so that code should work for
you.
HTH,
Robert
On 12/8/06, John DeeBee <[EMAIL PROTECTED]> wrote:
Hi,
I'm working on server-side from Axis2 v1.1 and I need to get the whole XML
request in my WS skeleton (and after) to make other XML parsing and to log
every message going in and out from my webapp.
In Axis2 v1.0, I wrote a method called setOperationContext() in my skeleton
which retireved the full XML request by using
"messageContext.getEnveloppe().toString()".
But now I'm working with v1.1 and it doesn't work anymore. So I delete my
setOperationContext() method and, in my WS operation, I write this code to
replace :
MessageContext contexteMessage =
MessageContext.getCurrentMessageContext();
setFluxXML(contexteMessage.getEnvelope().toString());
But "contexteMessage.getEnvelope().toString()" gives me only the beginning
and the end of the request, not the full content.
I tried to make a logging module as described in documentation but the
result is the quite the same. I have the full xml from WS response but not
for request.
Who have a solution before I getting mad ?
John
________________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions
! Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo! Questions/Réponses.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
