No, this is an internal clustering thing. Carbon kernel decides whether to load clustering from axis2.xml or from cluster.xml. No API changes. With carbon kernel, we will ship the cluster.xml.
Azeez On Thu, Jul 4, 2013 at 11:56 AM, Pradeep Fernando <[email protected]> wrote: > Hi Azeez, > +1 for the proposal. > > However how will this modification going to affect overall platform ? are > there going to be component level changes at large scale... > If so, im afraid it is too late to introduce this. We are stabilizing the > platform due to caching changes right now. Our plan is to create alpha > packs and go for platform branching straight away... > > > On Thu, Jul 4, 2013 at 11:24 AM, Afkham Azeez <[email protected]> wrote: > >> >> >> >> On Thu, Jul 4, 2013 at 11:23 AM, Amila Suriarachchi <[email protected]>wrote: >> >>> >>> >>> >>> On Thu, Jul 4, 2013 at 8:55 AM, Afkham Azeez <[email protected]> wrote: >>> >>>> While working on the new clustering API on the trunk, I thought it >>>> would not involve much work to simply decouple Carbon clustering from >>>> Axis2, rather than having two Clustering APIs. if everybody agrees, I can >>>> start working on it. I have already done that in a scratch area during the >>>> Carbon 5 work, and it is just a matter of bringing that code it. >>>> >>>> However, we need to update the docs. The configuration will be almost >>>> identical. >>>> >>> >>> +1. >>> >>> For carbon 4.3.0 we can remove axis2 clustering and deployment. >>> >> >> I'm actually thinking about doing this today :D >> >> >>> >>> thanks, >>> Amila. >>> >>> >>>> >>>> Thoughts? >>>> -- >>>> *Afkham Azeez* >>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>> Member; Apache Software Foundation; http://www.apache.org/ >>>> * <http://www.apache.org/>** >>>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>> twitter: >>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>> * >>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>> * >>>> * >>>> *Lean . Enterprise . Middleware* >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *Amila Suriarachchi* >>> >>> Software Architect >>> WSO2 Inc. ; http://wso2.com >>> lean . enterprise . middleware >>> >>> phone : +94 71 3082805 >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>** >> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * >> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >> * >> * >> *Lean . Enterprise . Middleware* >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Pradeep Fernando* > Associate Technical Lead;WSO2 Inc.; http://wso2.com > > blog: http://pradeepfernando.blogspot.com > m: +94776603662 > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
