Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (herse.apache.org: domain of davanum@gmail.com designates
 64.233.162.234 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Od+S6KzQ4LQekqU68FgALZq8cBd0QycbPDONP+JpQANeRbN8+f6kRw0Ec27/rKhhGGJLMR9PA1dYMiTN5pkaBrnPniyUsZ+GdBhu3ttTHamduwbzdKA86Zs7cE9s0GMrd8QXxHvUswcLczkU1wehcyJ852kaZnKy6Xs3DiiCOhI=
Message-ID: <19e0530f0705180718h7d2b3b13o2fb94085db79e5ea@mail.gmail.com>
Date: Fri, 18 May 2007 10:18:09 -0400
From: "Davanum Srinivas" <davanum@gmail.com>
Reply-To: dims@apache.org
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Clustering: Replicating properties in the context
 hierachy
In-Reply-To: <19e0530f0705180710q73495ac1wa20c7ee1a68b5a82@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <9b85c45f0705180416w294e6335y8b355c3d27128e46@mail.gmail.com>
	 <19e0530f0705180710q73495ac1wa20c7ee1a68b5a82@mail.gmail.com>

Only other thing i can think of is similar to you know the proxy
settings...have regexp based includes and excludes (on the key) in the
ClusterManager for the default properties we already have and allow
API access (and/or axis2.xml entries) for folks to add/delete from the
list of includes/excludes. that's that other extreme...

-- dims

On 5/18/07, Davanum Srinivas <davanum@gmail.com> wrote:
> Azeez,
>
> Did you already rule out a simple solution? If a service author wants
> a specific custom property to be available, then they can add a simple
> prefix to the key in the Map?
>
> thanks,
> dims
>
> On 5/18/07, Afkham Azeez <afkham@gmail.com> wrote:
> > We have a problem when it comes to replicating properties in our clustering
> > implementation.  There are some properties which are specific to a node,
> > specially properties in the ConfigurationContext.  Some properties are added
> > by different modules such as Sandesha2, Rampart to the ConfigurationContext.
> > One thing is that these objects are not serializable, and the other thing is
> > that these properties should not be replicated. Some information which are
> > specific to a node may be added to the ConfigurationContexts, and these
> > should never be replicated.
> >
> > So there should be some way to inform Axis2 about the properties that need
> > to be clustered and those that shouldn't be clustered.
> >
> > I suggest we introduce a new Map to AbstractContext called
> > clusterableProperties. Stuff that are added to this Map will be replicated,
> > and the service author/module author has to add the properties that need to
> > be replicated into the clusterableProperties Map.
> >
> > Thoughts?
> >
> > --
> > Thanks
> > Afkham Azeez
> >
> > http://www.wso2.org
> > GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760
>
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>


-- 
Davanum Srinivas :: http://davanum.wordpress.com

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