Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <7972173.1180522815667.JavaMail.jira@brutus>
Date: Wed, 30 May 2007 04:00:15 -0700 (PDT)
From: "Thilina Gunarathne (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Reopened: (AXIS2-2531) Make the outgoing SOAPEnvelope
 available to the service
In-Reply-To: <10726988.1176715815617.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AXIS2-2531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thilina Gunarathne reopened AXIS2-2531:
---------------------------------------


Hi Deepal,
This not about the client side... This request is to change the InOut message receiver implementations...

For an example in the case of RawXMLInOutMessageReceiver, it's about moving line 86 & line 92 to somewhere before line 83...So that users will be able to add SOAP headers to the outgoing envelope from the service implementation class it self...

   83             OMElement result = (OMElement) method.invoke(
                        obj, new Object[]{msgContext.getEnvelope().getBody().getFirstElement()});
                SOAPFactory fac = getSOAPFactory(msgContext);
    86           SOAPEnvelope envelope = fac.getDefaultEnvelope();

                if (result != null) {
                    envelope.getBody().addChild(result);
                }

    92            newmsgContext.setEnvelope(envelope);

> Make the outgoing SOAPEnvelope available to the service 
> --------------------------------------------------------
>
>                 Key: AXIS2-2531
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2531
>             Project: Axis 2.0 (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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org