[ http://issues.apache.org/jira/browse/AXIS2-1823?page=comments#action_12456477 ] Glen Daniels commented on AXIS2-1823: -------------------------------------
Hey folks: The rationale behind the switch to turn the cache on/off was that keeping a reference to the OC in a live object (a stub which is sitting around for a while and reused sporadically) might in many cases result in a significant amount of memory escaping garbage collection. If folks think it would be simpler to just cache all the time, I'm OK with that but we should keep this in mind as a potential hot spot. Shaoguang, I called the method "getLastOperationContext" because the operation is usually over by the time you call it. As for getting the MC instead, I think I'd prefer to keep it as is, retrieving the OC, because there may well be cases where you would like to examine the request message as well - or look at OC properties. Granted, you could get there by getting the response MC, then calling mc.getOperationContext().GetMessageContext(...), but I think this is a little cleaner. --Glen > 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]
