> > On 3/23/07, David Illsley <[EMAIL PROTECTED]> wrote:
> > > Um... a couple of questions..
> > > 1. How can we have multiple configuration contexts active in the same
> > > JVM if the factory hold the configuration context int a static field?
> >
> > Why would we need multiple configuration contexts for a single Axis2
> > instance?
>
> At the moment we can have more that 1 Axis2 instance running in a
> single JVM. I'd like to keep that capability and this proposal (I
> think) prevents that.
I don't think this will be a case in a production setup. Simply put, we
need some method to ensure that all objects within an Axis2 runtime use the
same configuration context.
I totally disagree. One of the things I really like about the Axis2
architecture is that there is such flexibility in how you deploy it.
> And yet you don't want to deprecate a method which returns a held
> reference to the ConfigurationContext?
The correct ConfigurationContext is linked with the MessageContext when
the MessageContext is created. So there is no need to remove this method.
Right, so I think the javadoc sould have to be modified to explain the
lifecycles and when it's safe to cache the ConfigurationContext
instances.
> What is the scenario that you're trying to support?
The ability to reload the configurations of a group of Axis2 nodes in a
cluster without having to restart them one by one.
This isn't something I see a need to support in this way. Why is it
not possible to load the new configuration into the existing objects?
David
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
