[ http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456470 ] Shaoguang Cong commented on AXIS2-1823: ---------------------------------------
Glen, I'm playing with the released version 2.1.1. So I cannot check the fix in the trunk. >From purely a user's view, I'll echo Sanjiva's comment on avoiding to use some >methods not so obvious to the app developer. Could just add the method as Deepal suggested, like ServiceClient.getCurrentOperationContext(); Or even ServiceClient.getCurrentMessageContext(). It's the returned MessageContext really matter in most cases if not all of the cases(e.g. retrieve soap header info). > 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
