Cool. It seems like this feature is an important feature to the community and hence I would like to prioritize this issue over others.
Thanks for all the feedback. Thanks, Ruwan On Wed, Jul 2, 2008 at 9:03 PM, Gary Rudolph <[EMAIL PROTECTED]> wrote: > > I just wanted to mention that I support multiple configs as well as a jar > deployment. > > We are moving to having our runtime be a maven pom.xml and to have our > deployments on the production servers actually download and run from maven > and write custom plugins to launch the apps. Without jar support this is not > ideal as we'd have to have the plugin actually explode it. > > I think our use cases if we scaled up would be in the range of 50-75 > proxies with multiple developers working on them. Doing this on a single > file is problematic. It would be useful start synapse with a comma delimited > list of configs to load. Or some parent config that has an "include" to the > other configs. > > Thanks, Gary > > > On Jul 2, 2008, at 7:14 AM, Scott Hoggarth wrote: > > It also does not allow you to define startup tasks. There are two Jira >> Issues that cover this SYNAPSE-347, SYNAPSE-346. >> >> Scott Hoggarth >> >> On 7/1/08 11:23 PM, "Asankha C. Perera" <[EMAIL PROTECTED]> wrote: >> >> Tanmay >>> >>>> For many Proxy Deployment, I >>>> have decided to use more than one Synapse config file (Synapse1.xml, >>>> Synapse2.xml , Synapse3.xml .... ) and use case wise I will distribute >>>> the >>>> <proxy> elements among multiple Synapse config files, and the develop a >>>> startup script (using XQuery )which will aggregate all config elements >>>> from >>>> different synapse config files into a single Synapse.xml file . >>>> >>>> Is it possible for Synapse to specify multiple config files during >>>> startup >>>> like Springframework ( where you can use more than one beans config file >>>> like >>>> applicationContext1.xml,applicationContext2.xml,applicationContext3.xml, >>>> and >>>> so on )? This will make maintenance and developers' easy over a giant >>>> config file. >>>> >>>> You can split elements in a large synapse.xml into different files.. >>> like sequences, endpoints etc..(e.g. >>> http://synapse.apache.org/Synapse_Samples.html#Sample10) But this does >>> not allow you [yet] to define proxy services.. so your suggestion is good >>> >>> asankha >>> >> >> > -- Ruwan Linton http://wso2.org - "Oxygenating the Web Services Platform" http://ruwansblog.blogspot.com/
