[ http://issues.apache.org/jira/browse/AXIS2-938?page=comments#action_12423995 ] Davanum Srinivas commented on AXIS2-938: ----------------------------------------
Here's my train of thought: - 3 changes to classes under jaxws look ok. - 3 new classes (ThreadContext*.java) look ok. - But, those 3 classes are not used in modules/core so they can be moved to modules/jaxws (addThreadContextMigrator can take in an Object - if push comes to shove) - Now, there is only one change left in modules/core which is the change to AxisConfiguration.java - There are 3 methods in that change, which is to maintain the List of threadContextMigrators. - First of all, that LinkedList can be added as a get/set property with a special key in ConfigurationContext, then you won't need to touch AxisConfiguration.java at all. - Since AxisConfiguration is not meant to hold runtime information (AxisConfiguration is only for loading and deploying stuff) and ConfigurationContext is...So ConfigurationContext is a better location to store that LinkedList. So, if you move the LinkedList to ConfigurationContext, then all the changes will be limited to modules/jaxws which is perfect because the new Interface class is not really usable by anyone else other than jaxws as the hooks are not called/used anywhere in the core anyways. What do you think? thanks, dims > Plugpoint to allow for migration between context and TLS > -------------------------------------------------------- > > Key: AXIS2-938 > URL: http://issues.apache.org/jira/browse/AXIS2-938 > Project: Apache Axis 2.0 (Axis2) > Issue Type: New Feature > Components: core, jaxws > Reporter: Bill Nagy > Assigned To: Bill Nagy > Attachments: tlsmigrator.patch > > > We have an issue with some APIs (e.g. security, Tx) requiring that data be > present on Thread Local Storage (TLS). I believe that we can work around (at > least for now) needing to migrate information between threads, and can simply > get away with storing it in one of the contexts and then moving it to TLS > before we get into user space (i.e. up through the service programming model) > and then back again if need be. -- 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]
