[ http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456512 ] Sanjiva Weerawarana commented on AXIS2-1823: --------------------------------------------
+1 for getLastOperationContext instead of getLastMC() as the latter is relatively meaningless esp. if async invocations are in place. W.r.t. the caching flag- I didn't look at the code yet but I assume you just made the OC variable an instance var of the service client object right? If so I'm fine with removing the caching flag as once the service client is dropped (that is when the stub is dropped) all state will be GC'ed. Alternatively, how about keeping it but leaving it with default on? Then if someone really doesn't want those message contexts hanging around even for a bit they can turn it off. > 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]
