If we use two property bags, the WS author has to be cluster aware, to make a WS clusterable, he'd have to change many places.
-- Azeez On 5/20/07, Jaliya Ekanayake <[EMAIL PROTECTED]> wrote:
Can we not use two property bags for this? MHO is this prefixes and suffixes may produce hard to debug bugs. -jaliya ----- Original Message ----- *From:* Afkham Azeez <[EMAIL PROTECTED]> *To:* [email protected] *Sent:* Saturday, May 19, 2007 8:48 AM *Subject:* Re: [Axis2] Clustering: Replicating properties in the context hierachy On second thoughts, lets make it a simple string not a regex. If we use regex, special characters (specially the period, which may be used regularly) have to be escaped by the user. To keep things simple, let's allow only prefixes, suffixes & exact matches; 1. Prefix - e.g. local_* ==> all properties beginning with the string "local_" 2. Suffix - e.g. *_local ==> all properties ending with the string "_local" 3. Exact match - e.g. Sandesha2PolicyBean -- Azeez On 5/19/07, Afkham Azeez <[EMAIL PROTECTED]> wrote: > > > > On 5/18/07, Davanum Srinivas < [EMAIL PROTECTED]> wrote: > > > > Sounds good to me Azeez. > > - Should the name(s) be regexp expressions or just a simple "*" means > > (one or more characters)? > > > Let's make it regex. It will be easier to handle it with regex. > > - So is there a implicit <include name="*">? Should we allow folks to > > set includes as well (like in ant tasks). Guess it's an overkill. > > > I think there is no need to have an <includes />. Whatever which is not > explicitly excluded is included. > > thanks, > > dims > > > > On 5/18/07, Afkham Azeez <[EMAIL PROTECTED]> wrote: > > > Great idea Dims. > > > > > > So under the ContextManager entry in the axis2.xml, we can specify > > the > > > patterns of the property name which have to be excluded from > > replication. > > > e.g. > > > > > > <ContextManager > > > class="org.apache.axis2.cluster.tribes.context.TribesContextManager > > > "> > > > <Replication> > > > <Defaults> > > > <excludes name="foo.bar.*"/> > > > </Defaults> > > > <ConfigContextProperties> > > > <excludes name="my.sandesha.*"/> > > > ... > > > </ConfigContextProperties> > > > <ServiceGroupContextProperties> > > > <excludes name="..."/> > > > </ServiceGroupContextProperties> > > > <ServiceContextProperties> > > > <excludes name="..."/> > > > </ServiceContextProperties> > > > <Replication> > > > </ContextManager> > > > > > > So any of the context properties matching a particular property will > > not be > > > replicated. > > > > > > -- Azeez > > > > > > > > > On 5/18/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > > > > > > > > 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 < [EMAIL PROTECTED] > 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 < [EMAIL PROTECTED] > 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: > > > [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > -- > > > > > > 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 > > > > > > -- > 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 Afkham Azeez http://www.wso2.org GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760
