axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-1823) Client API needs a method to access Current Message Context
Date Thu, 07 Dec 2006 06:42:21 GMT
    [ http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456307 ] 
            
Sanjiva Weerawarana commented on AXIS2-1823:
--------------------------------------------

Do we really need setCachcingOperationContext()?? When I looked at it I didn't think there
would be any cost with saving the opcontext. If so why not just have it be available. 

It seems to me this should be true anyway by default.

> Client API needs a method to access Current Message Context
> -----------------------------------------------------------
>
>                 Key: AXIS2-1823
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1823
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: client-api
>            Reporter: Shaoguang Cong
>         Assigned To: Glen Daniels
>
> The generated client stub doesn't have a way to access MessageContext or SOAPHeader.
 Client would like to access the header upon returned from the service.  It's ideal to add
a getter method in the client stub or Service Client class.

-- 
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message