axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Passmore" <>
Subject Re: Handlers and SOAP message re-writing
Date Thu, 05 Sep 2002 20:14:02 GMT
I have tried this, but was not able to get it working either. I really need
to do this!


----- Original Message -----
From: "Allegar Robert" <>
To: <>
Sent: Thursday, September 05, 2002 1:51 PM
Subject: RE: Handlers and SOAP message re-writing

> Ok -- I've tried the same thing under RC1 and it still doesn't work. My
> question to the group: has anyone successfully re-written the SOAP body
> code that's inside a handler?
> Rob
> -----Original Message-----
> From: Allegar Robert []
> Sent: Thursday, September 05, 2002 12:57 PM
> To:
> Subject: RE: Handlers and SOAP message re-writing
> > I would think you need to add the node to the RESPONSE message, not the
> > request message.
> I don't know if this is the case .. the request does not become the
> until we are past the pivot point -- and we don't get to the pivot point
> until the actual web service is invoked. So if my handler means to
> all messages and re-write the incoming request transparently, it should
> re-write the request and not the response. Otherwise my handler would be
> changing the message that the client who invoked the service would
> The documentation is unclear on this point -- am I correct in assuming
> the 'request' message becomes the 'response' message after the pivot point
> has been reached? Or does the request/response convention exist in
> as well (i.e. a request comes in to the handler and a response is sent out
> of the handler).
> Which context does the nomenclature apply to? The call itself, or the
> handler.
> Rob
> -----Original Message-----
> From: Rob Allegar []
> Sent: Thursday, September 05, 2002 12:14 PM
> To: ''
> Subject: Handlers and SOAP message re-writing
> Is the SOAP message considered read-only when it's being handled by the
> handlers? I'm trying to use a value in the header I receive to look up a
> value to place in the body. I've extracted out the essence of this in the
> following lines of code:
> Message requestMessage = context.getRequestMessage();
> SOAPEnvelope envelope = requestMessage.getSOAPEnvelope();
> SOAPElement element = envelope.addChildElement("testElement");
> element.addTextNode("testElementNode");
> This code exists in a handler. Unfortunately, the SOAP message that's
> leaving the handler does not contain the new element I've just added -- it
> almost appears the message is read-only, though no faults or exceptions
> thrown.
> The thing that troubles me is that this code works as it should under
> Weblogic 7.0's webservice impl. Am I doing something wrong, calling the
> wrong APIs or is this a bug?
> Regards,
> Rob

View raw message