Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (hermes.apache.org: domain of davidillsley@gmail.com
 designates 64.233.182.191 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=NvCG0Rlq7xf4ghw5QL9qDpQ2DdCiMc3/zDqkIiVkcpy9nM1SPur0x18xdOEb+gB+zerwY7Dd2L1Gu1pDOmXr0FBppnnlMisaFqMVVfEm8IFdtgFYwwRZmnewnIcUOttDfYafYKM33t7KrJxj9sq63A/WE2aH7m4KUGbXEAl/Tao=
Message-ID: <9abd5e730703230211m667e4a0h731c98f29a254fd1@mail.gmail.com>
Date: Fri, 23 Mar 2007 09:11:00 +0000
From: "David Illsley" <davidillsley@gmail.com>
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Fwd: Introducing
 ConfigurationContextFactory.getConfigurationContext()
In-Reply-To: <46037486.4070701@opensource.lk>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <9b85c45f0703222310s21727c8fx88f070dad2090bac@mail.gmail.com>
	 <9b85c45f0703222319u65fa3563od1d2d0179f944249@mail.gmail.com>
	 <9d4ec10b0703222324n496489e5ted5fad758564785@mail.gmail.com>
	 <46037486.4070701@opensource.lk>

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?
2. DO you intend to deprecate methods such as
MessageContext.getConfigurationContext()?

David

On 23/03/07, Deepal Jayasinghe <deepal@opensource.lk> wrote:
> I have no objection on doing this ,
> but inside ListenerManager we keep static reference to current
> ConfigurationContext , cant we use that to achieve your goal ?
>
> In the other hand it is nice to have getConfigurationContext method in
> ConfigurationContextFactory , then all the ConfigurationContext related
> logic will be there in that class.
>
> Thanks
> Deepal
>
> Chamikara Jayalath wrote:
>
> > [Added the prefix]
> >
> > ---------- Forwarded message ----------
> > From: *Afkham Azeez* <afkham@gmail.com <mailto:afkham@gmail.com>>
> > Date: Mar 23, 2007 11:49 AM
> > Subject: Re: Introducing
> > ConfigurationContextFactory.getConfigurationContext()
> > To: Apache AXIS C Developers List <axis-c-dev@ws.apache.org
> > <mailto:axis-c-dev@ws.apache.org>>
> >
> > Sorry. This was intended for the Axis2 Java Dev list.
> >
> > -- Azeez
> >
> >
> > On 3/23/07, *Afkham Azeez* < afkham@gmail.com
> > <mailto:afkham@gmail.com> > wrote:
> >
> >     I'm currently implementing the Configuration management portion of
> >     Axis2 clustering. This allows us to switch to a new configuration,
> >     without restarting Axis2. However, I discovered that  there are
> >     pointers from many classes to the ConfigurationContext, hence
> >     switching to a new ConfigurationContext & AxisConfiguration is messy.
> >
> >     Therefore I propose that we cache the ConfigurationContext
> >     instance in ConfigurationContextFactory. I am introducing the
> >     following to the ConfigurationContextFactory:
> >
> >     ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
> >
> >         /**
> >          * The cached instance of the ConfigurationContext
> >          *
> >          * Other objects should not hold referencs to the
> >     ConfigurationContext, and should ALWAYS
> >          * get ConfigurationContext from this factory. This is to
> >     ensure that the ConfigurationContext
> >          * can be seamlessly switched.
> >          */
> >         private static ConfigurationContext configurationContext;
> >
> >         /**
> >          * Return the cached ConfigurationContext instance
> >          *
> >          * @return The cached ConfigurationContext instance
> >          */
> >         public static ConfigurationContext getConfigurationContext() {
> >             return configurationContext;
> >         }
> >     ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
> >
> >
> >     So, if someone calls a createConfigurationContext method on this
> >     factory, the old configurationContext instance will be replaced
> >     with the new one. Any object which wishes to get hold of the
> >     ConfigurationContext SHOULD call
> >     ConfigurationContextFactory.getConfigurationContext(), and should
> >     never hold a pointer to the ConfigurationContext. This will ensure
> >     that when the ConfigurationContext is changed, all objects in the
> >     system will use the correct ConfigurationContext object, and that
> >     the old object will get garbage collected.
> >
> >     What do you think about this approach?
> >
> >     --
> >     Thanks
> >     Afkham Azeez
> >
> >     http://www.wso2.org
> >     GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760
> >
> >
> >
> >
> > --
> > Thanks
> > Afkham Azeez
> >
> > http://www.wso2.org
> > GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760
>
>
> --
> Thanks,
> Deepal
> ................................................................
> "The highest tower is built one brick at a time"
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
David Illsley - IBM Web Services Development

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org