[ http://issues.apache.org/jira/browse/AXIS2-938?page=comments#action_12424587 ] Bill Nagy commented on AXIS2-938: ---------------------------------
(Sorry that I'm a little late to the discussion; I just switched machines and apparently my mail filtering is screwed up.) The plugpoint was indeed meant to be PM-agnostic, and I know for a fact that when Tuscany integrates with Axis2 they will need this as well. As Nick pointed out, the invocations have to happen at the PM layer, as the PM may introduce thread-switches of its own, and that's the only place that will know when all of those have been completed or will know before they start. As to putting the LinkedList into the AxisConfiguration vs. the ConfigurationContext, I had likened the migrators to modules, transports, phases, etc. all of which reside in the AxisConfiguration. At least on the client side, migrators are going to have to be statically registered/deployed, as they need to be invoked high up in the PM and not much of the engine will have executed at that point in time. If you still think that they belong in the ConfigurationContext, then I'm happy to move the List. -Bill > 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]
