Yes, we should not be doing any drastic changes now. We can push them in after the initial release. IMHO it is better if we can still provide a Message Broker (maybe a separate JVM as you have mentioned) for the demo scenarios, or else a user who is simply trying to run the demo will have to configure the MB.
On Thu, Aug 22, 2013 at 9:11 AM, Lakmal Warusawithana <[email protected]>wrote: > Make sure, you don't push these changes, until you are confident that this > not break any other flow. I would like to have feature freeze, since we > plan to do a release next week. > > sent from phone > On Aug 21, 2013 11:45 PM, "Isuru Perera" <[email protected]> wrote: > >> Hi all, >> >> Just a heads up! >> >> I will be doing some changes to Topology sync logic. >> >> Related JIRAs >> https://issues.apache.org/jira/browse/STRATOS-48 >> https://issues.apache.org/jira/browse/STRATOS-52 >> >> Objectives: >> >> 1. Common Message Broker configuration in all Stratos Products (Cloud >> Controller, Stratos Controller and ELB) >> 2. Support for other message brokers. Planning to test with Apache >> ActiveMQ and WSO2 Message Broker first. >> >> >> I will let you all know more details later. >> >> Thanks! >> >> -- >> Isuru Perera >> Senior Software Engineer | WSO2, Inc. | http://wso2.com/ >> Lean . Enterprise . Middleware >> >> about.me/chrishantha >> > -- Thanks and Regards, Isuru H.
