Hi Kishanthan, Yes we are giving versioning only for synapse xml file. Not for the services that in synapse file.
So we thought to give user to have different version of synapse files. So user can deploy one of synapse file to one staging server and different one for other stage. But only one synapse file can be in one stage. thanks On Sun, Mar 17, 2013 at 10:45 PM, Kishanthan Thangarajah < [email protected]> wrote: > Hi Harsha, > > On Wed, Mar 13, 2013 at 9:19 AM, Harsha Thirimanna <[email protected]>wrote: > >> Hi, >> >> This is regarding, do the version of synapse file that generated by the >> AppFactory as a new Artifact. Finally we got the >> the decision to restrict do the version of synapse file in AppFactory >> because of we can deploy only one synapse file in ESB for >> one tenants at a time and the rename the name of proxy and others in >> inside of synapse file is not possible. >> >> I want to mention another point. We can do the version of synapse file >> without changing the file content like proxy name and other >> stuff. Then user can have the multiple version of synapse file without >> changing the proxy name and other names but having other >> changes of him. >> > > I'm just curious to know how this can be done? Is it going to at per > tenant level? > > Also I believe here you are talking about versioning support of > synapse.xml but not others such as proxies etc. Because proxy services are > also axis2 services and axis2 will not allow to have two service with the > same name as it will throw service already exists error. > > So user can then deploy specific version of synapse file to the staging >> servers. So in different stages can have >> different synapse file version too if user wants. >> > > Does this mean that a user can also have two or more different versions of > synapse configuration (synapse.xml) per stage, say development, and select > one of the version to be available at that stage? > > Thanks, > Kishanthan. > > How about the possibility of doing these ? Implementation can be done for >> both of >> above scenarios with only changing few line of code. >> >> thanks >> Harsha Thirimanna >> >> >> >> >> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Kishanthan Thangarajah* > Software Engineer, > Development Technologies Team, > WSO2, Inc. > lean.enterprise.middleware > > Mobile - +94773426635 > Blog - *http://kishanthan.wordpress.com* > Twitter - *http://twitter.com/kishanthan* > -- *Harsha Thirimanna* Senior Software Engineer; WSO2, Inc.; http://wso2.com * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 71 5186770 blog: *http://www.mind4web.org/ <http://www.apache.org/>* twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>** harshathirimann linked-in: **http: <http://lk.linkedin.com/in/afkhamazeez>**// www.linkedin.com/pub/harsha-thirimanna/10/ab8/122* * * *Lean . Enterprise . Middleware* * *
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
