Hi,
I came across with the same scenario that Senaka explaining here, while
configuring FIX business scenarios I had to keep multiple synapse
configuration files. Workaround I found for that is to create the config
files inside ${ESB_HOME}/repository/conf/sample and name the config file
as synapse_sample_<number>.xml, when starting synapse pass it as a CMDL
argument -sample <number> and it took the relevant config file. (e.g
config file name synapse_sample_900.xml , $> startup ./synapse.sh
-sample 900)
Asanka A.
Senaka Fernando wrote:
> 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
>
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
