Hi folks, As I mentioned in one of my notes a while ago, 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.
Unless there are objections, I'm going to create a new Interface, org.apache.axis2.util.ThreadContextMigrator, with two methods, void migrateContext(MessageContext messageContext) and void flowComplete (MessageContext messageContext), add a List and accessor methods to the AxisConfiguration to store instances of the Interface, and add the appropriate invocations in the JAX-WS code to invoke them. (If there are no registered instances, then the only cost is checking to see if the List is empty.) The second method is needed to allow for cleanup of the TLS after execution has completed. Questions/comments? -Bill --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
