axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas" <>
Subject Re: [jira] Commented: (AXIS2-938) Plugpoint to allow for migration between context and TLS
Date Mon, 31 Jul 2006 18:58:53 GMT

If we decide to mode the whole thing into modules/core, then i will
have no problem keeping the methods for migrators and make it similar
to modules, transports, phases etc.

Here's my problem, the Patch does not reflect the intention. If you
check it in as-is right now. Anyone using the core module and *NOT*
using module/jaxws will scratch their heads as their entry points are
*NEVER* called from the code.

Do you see the problem?


On 7/31/06, Bill Nagy (JIRA) <> wrote:
>     [ ]
> 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
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message