[ 
http://issues.apache.org/jira/browse/AXIS2-242?page=comments#action_12330387 ] 

Sanjiva Weerawarana commented on AXIS2-242:
-------------------------------------------

But that's the correct behavior .. if there is no RelatesTo then there's no 
existing operation context. 

Going back to your original comment, it should not be the case that 
msgContext.getOperationContext() != null and the resulting operationContext 
does not have any message contexts in it!

> A client side handler in the response(in) flow cannot access the request(out) 
> message context
> ---------------------------------------------------------------------------------------------
>
>          Key: AXIS2-242
>          URL: http://issues.apache.org/jira/browse/AXIS2-242
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>     Reporter: Ruchith Udayanga Fernando

>
> Seems like its not possible to access the out message context of a web 
> service invocation, from an inflow handler placed in the Dispatch or 
> PostDispatch phases. - I experienced this with a blocking in-out message on a 
> single channel.
> In the above instances the we can access the operation context from the 
> message context in the inflow with:
> OperationContext opCtx = msgContext.getOperationContext();
> but both 'inMessageContext' and 'outMessageContext' references were null.
> I ran into this problem when updating the security module, where we have to 
> communicate the signature 'values' of the outgoing message to the handler in 
> the inflow to verify against the values sent in the 
> wsse11:SignatureConfirmation element.
> The workaround used for this situation is to have a ThreadLocal reference in 
> a util class to hold the values set by the outflow handler (WSDoAllSender) 
> and to be picked up by the inflow handler (WSDoAllReceiver)
> What do u folks think about this?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to