On Wed, 2006-07-12 at 09:40 -0400, Bill Nagy wrote: > Hi dims, > > Sure. You are correct, there is no TLS code currently in Axis2. > However we (IBM) have several cases (e.g. security) where we need to > migrate information between the Axis2 contexts and TLS. For example, we > have identity APIs that rely upon tokens being placed in TLS. While we > can have the handler place the information in the MessageContext for > example, we need to move it to TLS before we enter "user space," so that > if the user invokes one of our security APIs the information will be > available. (We also need to make sure that the info is removed from TLS > when we're done, hence the flowComplete() method.)
So is this basically a utility class that a specific handler invokes? Or are you suggesting that people register these "migrators" against a handler and then they get invoked upon entry/exit? I guess the lifecycle and programming model for TCMigrators is not clear enough to me yet! Sanjiva. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
