Hi Sanjiva,

Unless I'm not explaining it well, the only piece that is different from
what I had described earlier
(http://marc.theaimsgroup.com/?l=axis-dev&m=115270290506219&w=2) is the
interface; there are now two extra methods to make it more clear to
someone who is writing a migrator (or reading the PM-level code) what
the migrator is supposed to be doing (i.e. moving info from the context
to the TLS or vice versa.)

If that doesn't help, RTFP 8-].

-Bill

On Mon, 2006-07-31 at 23:53 +0530, Sanjiva Weerawarana wrote:
> On Mon, 2006-07-31 at 10:41 -0700, Bill Nagy (JIRA) wrote:
> > (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.
> 
> I haven't had a chance to go thru the patch yet .. any chance of sending
> a description of it? From the discussion I see its somewhat diff from
> what was originally suggested (which is cool of course). If u want to
> tell me RTFP I'll accept it :).
> 
> Sanjiva.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to