There is one more problem even going with this property/configuration based approach.
In Our case Cassandra server must be started before starting andes related features. So if we go with this approach In a Cluster enabled mode User will have to 1) Change the andes-config.xml in which he will enable clustering (and do other config changes to point to zookeeper , Cassandra server etc ) 2) Start the server with that system property used by Cassandra component (Or if its a conifg change that config file) 2 places to do the same change. So its ugly. I think for BAM same problem will be there. Any ideas to fix this in a proper way ? thanks, Charith On Wed, Apr 4, 2012 at 12:09 PM, Pradeep Fernando <[email protected]> wrote: > Hi, > > basically its bundles that get activated. There is not feature concept in > runtime. Configuration based approach is the only way to handle this kind > of scenario. However configuration can be done using, > property/xml file > system property > Some other bundle configuring the target through configuration admin > service. > > thanks, > --Pradeep > -- Charith Dhanushka Wickramarachchi Software Engineer WSO2 Inc http://wso2.com/ http://wso2.org/ blog http://charithwiki.blogspot.com/ twitter http://twitter.com/charithwiki Mobile : 0776706568
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
