axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srinath Perera (JIRA)" <>
Subject [jira] Resolved: (AXIS2-2531) Make the outgoing SOAPEnvelope available to the service
Date Tue, 21 Dec 2010 15:59:01 GMT


Srinath Perera resolved AXIS2-2531.

    Resolution: Fixed

Currently this can be done by adding a Handler. If needed set it as a property to operation
context, get it from the handler and set it. 

There has not been any other  interest on the issue, and since there is another way of doing
it, I am going to resolve this. 

> Make the outgoing SOAPEnvelope available to the service 
> --------------------------------------------------------
>                 Key: AXIS2-2531
>                 URL:
>             Project: Axis2
>          Issue Type: Improvement
>            Reporter: Thilina Gunarathne
>            Assignee: Deepal Jayasinghe
>            Priority: Critical
> Currently service authors cannot set headers to the outgoing envelope from the service..
 The reason is that in the InOut message receivers, we create the outgoing SoapEnvelope after
invoking the business logic.. 
>                 OMElement result = (OMElement) method.invoke(
>                         obj, new Object[]{msgContext.getEnvelope().getBody().getFirstElement()});
>                 SOAPFactory fac = getSOAPFactory(msgContext);
>                 SOAPEnvelope envelope = fac.getDefaultEnvelope();
>                 if (result != null) {
>                     envelope.getBody().addChild(result);
>                 }
>                 newmsgContext.setEnvelope(envelope);
> It would be great if we can make the envelope available to the service by moving the
newmsgContext.setEnvelope(envelope); and the related code to some where before the method.invoke...

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message