Hi Ruwan, ok, removing system properties or at least reducing the number of system properties can reduce the configuration complexity. So I understand this point. On the other hand you need to find a managable way for your customers to dynamically switch between different configurations (keeping in mind both standalone and WAR-installations). When speaking about configurations I am referring not only to synapse.xml but basically every setting split across a number of different configuration files (like port settings for listeners, rmi registry, binding addresses and so on).
So for example if you are going to remove the -Dsynapse.xml option, what is the substitute of this? I guess currently a lot of customers are relying on this feature because they have a need to separate the synapse.xml from the installation (e.g. to put it in a shared network location to be accessable by different nodes of a "WSO2 ESB cluster". I would like to see open discussions about such important topics! Regards, Eric > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Ruwan Linton > Sent: Tuesday, August 12, 2008 11:39 AM > To: [email protected] > Subject: Re: [esb-java-dev] Specifying alternate synapse.xml when starting > ESB > > Hi Senaka, > > We do not recommend to use system properties, and the -Dsynapse.xml is > still valid because we had to assure the backwards compatibility. System > properties are sort of deprecated and will be removed in a future release. > > Thanks, > Ruwan > > Senaka Fernando wrote: > > Hi again Ruwan, > > > > I believe that this involves a minor fix to the wso2-esb.sh, which > > looks more elegant than the axis2.xml approach. > > > > if [ "$1" = "-synapseXML" ]; then > > SYNAPSE_XML=-Dsynapse.xml=$2 > > fi > > > > Also the portion of code > > > > ---- > > if [ "$1" = "-xdebug" ]; then > > XDEBUG="-Xdebug -Xnoagent > > -Xrunjdwp:transport=dt_socket,server=y,address=8000" > > fi > > > > if [ "$1" = "-sample" ]; then > > > > SYNAPSE_XML=- > Dsynapse.xml=$ESB_HOME/repository/conf/sample/synapse_sample_$2.xml > > fi > > > > if [ "$1" = "-serverName" ]; then > > SERVER_NAME="-DserverName=$2" > > fi > > > > if [ "$3" = "-xdebug" ]; then > > XDEBUG="-Xdebug -Xnoagent > > -Xrunjdwp:transport=dt_socket,server=y,address=8000" > > fi > > > > if [ "$3" = "-sample" ]; then > > > > SYNAPSE_XML=- > Dsynapse.xml=$ESB_HOME/repository/conf/sample/synapse_sample_$4.xml > > fi > > > > if [ "$3" = "-serverName" ]; then > > SERVER_NAME="-DserverName=$4" > > fi > > > > if [ "$5" = "-xdebug" ]; then > > XDEBUG="-Xdebug -Xnoagent > > -Xrunjdwp:transport=dt_socket,server=y,address=8000" > > fi > > > > if [ "$5" = "-sample" ]; then > > > > SYNAPSE_XML=- > Dsynapse.xml=$ESB_HOME/repository/conf/sample/synapse_sample_$6.xml > > fi > > > > if [ "$5" = "-serverName" ]; then > > SERVER_NAME="-DserverName=$6" > > fi > > ------- > > > > can simply be implemented as a for loop that iterates 3times isn't it. > > :)... > > > > Regards, > > Senaka > > > > On Tue, Aug 12, 2008 at 11:54 AM, Ruwan Linton <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > Asanka and Senaka, > > > > On the latest trunk of synapse, you can specify this as a axis2.xml > > parameter with the name "SynapseConfig.ConfigurationFile", but for > > this > > to be effective the VM argument has to be null. > > > > Thanks, > > Ruwan > > > > Asanka Abeysinghe wrote: > > > 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] <mailto:[email protected]> > > > http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev > > > > > > > > > > > > _______________________________________________ > > Esb-java-dev mailing list > > [email protected] <mailto:[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 _______________________________________________ Esb-java-dev mailing list [email protected] http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
