Folks, Since there is no negative feedback on implementing this I have implemented this on the trunk as well as on the 1.3 branch.
Thanks, Ruwan On Mon, Aug 10, 2009 at 10:01 PM, Ruwan Linton <[email protected]>wrote: > Yes, Eric. As Hiranya explained it is configurable and you could keep that > some where out of the ESB installation directory. I think the best practice > for the production deployment has to be keeping that on a separate location. > > Thanks, > Ruwan > > > On Mon, Aug 10, 2009 at 7:31 PM, Hiranya Jayathilaka <[email protected] > > wrote: > >> Hi Eric, >> >> On Mon, Aug 10, 2009 at 6:15 PM, Hubert, Eric >> <[email protected]>wrote: >> >>> Hi Ruwan, >>> >>> >>> >>> I’m also +1 on this one. I hope it will still be possible to move the >>> whole synapse-config directory out of the directory structure to any place >>> the user wants it to have like it is now possible for synapse.xml. >>> >> That is correct. You can have the directory wherever you like in the file >> system. I have recently added a new sample (sample 600) which demonstrates >> this feature. You can have a look if you want more information. You need to >> pass the directory path to Synapse as an argument. >> >> Thanks, >> Hiranya >> >> >>> >>> >>> Regards, >>> >>> Eric >>> >>> >>> >>> >>> ------------------------------ >>> >>> *From:* Ruwan Linton [mailto:[email protected]] >>> *Sent:* Monday, August 10, 2009 7:47 AM >>> *To:* [email protected] >>> *Subject:* [PROPOSAL] Hierarchical directory based configuration as the >>> default configuration >>> >>> >>> >>> Folks, yet another proposal :-) >>> >>> Shall we make the hierarchical directory based synapse configuration to >>> be the default configuration mechanism? It will give Synapse many >>> advantages while we can make it have no disadvantages by supporting a >>> synapse.xml file inside the root of the configuration hierarchy. >>> >>> So what I am proposing is that we create the >>> repository/conf/synapse-config/ directory by the build and treat that as the >>> synapse configuration root which will have sup directories to hold >>> individual artifacts like sequences, endpoints and so on. At the same time >>> we should support a synapse.xml file to be embeded with multiple elements in >>> the configuration root (in this case the direcotry "synapse-config") >>> supporting the existing behaviour. >>> >>> With this we can get rid of the registry.xml and the local-entries.xml >>> files that we have on the configuration root and bring them into the >>> synapse.xml itself. >>> >>> This would make the configuration nicely placed with different levels as >>> well as supporting the flat file at the same time by default. >>> >>> WDYT? >>> >>> >> >> >> -- >> Hiranya Jayathilaka >> Software Engineer; >> WSO2 Inc.; http://wso2.org >> E-mail: [email protected]; Mobile: +94 77 633 3491 >> Blog: http://techfeast-hiranya.blogspot.com >> > > > > -- > Ruwan Linton > Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb > WSO2 Inc.; http://wso2.org > email: [email protected]; cell: +94 77 341 3097 > blog: http://ruwansblog.blogspot.com > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: [email protected]; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com
