Done [1]. I guess BAM is already using dep sync for toolboxes, it is just the Hive scripts that are stored in the registry for some reason. Will fix if there is anything to be fixed.
[1] https://wso2.org/jira/browse/BAM-1244 Cheers, Anjana. On Wed, Jun 12, 2013 at 3:36 PM, Srinath Perera <[email protected]> wrote: > Anjana, we should fix this. Lets create a issue > > --Srinath > > > On Sat, Jun 8, 2013 at 4:55 AM, Amila Suriarachchi <[email protected]> wrote: > >> hi, >> >> According to this[1] BAM uses registry mounting to share the analyser >> artefacts among the nodes. >> >> But with the carbon 4.0.0 based products recommended approach is to use >> the dep synch. So what I would like to suggest is to use the dep sync to >> synchronise the artefacts and deplorer can decide whether to run the >> analysers or not according to the state of the zookeeper Agent. >> >> And also we need to have the developer studio support for bam tool boxes >> so that it can be deployed as a .car file. >> >> WDYT? >> >> >> [1] >> http://docs.wso2.org/wiki/display/BAM230/Patially-Distributed%2C+High-Availability+BAM+Setup >> >> -- >> *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 >> >> > > > -- > ============================ > Srinath Perera, Ph.D. > http://people.apache.org/~hemapani/ > http://srinathsview.blogspot.com/ > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Anjana Fernando* Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
