Hi Ruwan, This is the scenario. The synapse.xml by nature is passed in as a VM argument. However,
1. We do not have the possibility to specifying optional VM arguments during the ESB start up. 2. When creating an extension to ESB/Syanpse, perhaps a sample or a demo application that uses a specific synapse.xml requires a modified startup script for Synapse/ESB. 3. There can be a scenario where a user maintains two synapse configurations (synapse.xml files) one of which is for debugging purposes for application logic (just assume), wouldn't it be better if he had the choice to specify the path to synapse config instead of replacing the default instance. * The requirement is rather to asset debugging, demonstarting or any other similar activity. Regards, Senaka On Tue, Aug 12, 2008 at 5:51 AM, Ruwan Linton <[EMAIL PROTECTED]> wrote: > Senaka Fernando wrote: > > Hi all, > > > > Wouldn't it be better to make it possible to specify an alternate > > synapse.xml when starting ESB? > What exactly do you refer as an alternative synapse.xml and which > conditions do you think it is important? > > Thanks, > Ruwan > > > > Regards, > > Senaka > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Esb-java-dev mailing list > > [email protected] > > http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev > > > > > _______________________________________________ > Esb-java-dev mailing list > [email protected] > http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev >
_______________________________________________ Esb-java-dev mailing list [email protected] http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
