You can also use a single xml configuration file if you prefer for all your servicemix endpoints:
http://svn.apache.org/viewvc/incubator/servicemix/trunk/deployables/serviceengines/servicemix-lwcontainer/src/test/resources/org/apache/servicemix/lwcontainer/su2-src/servicemix.xml?revision=584990&view=markup&pathrev=584990 On Dec 20, 2007 7:27 PM, Robert Thullner <[EMAIL PROTECTED]> wrote: > Hi > > I have now been playing and working with ServiceMix a few weeks. But I > still > have one question targeting the manageability and maintainability of my > configurations. > > Assuming that I have 20 or more service units in my service assembly, so > that I would also have 20 xbeans.xml, pom.xml, etc. files where my service > units are configured (services, endpoints, routes, etc.). For me that > would > lead into a real mass of configuration files that have to be managed and > maintained somehow. However I find it painful to keep the overview of such > a > mass of files. > > Do you advises a way or a tool how to keep the management complexity of > huge > service assemblies low so that I do not have to keep track of and maintain > a > lot of xml files if any changes in an environment occur? > > Thanks for any thoughts and suggestions > Robert > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
