Please don't take my response as given, as I am a beginner as well. I think one of the limitations of using servicemix.xml comes with its intrinsic nature of being static. For example, if you have deployed your application in a production environment and wanted to alter it, you would want to hot deploy or undeploy a well-tested service assembly, instead of manually modifying your servicemix.xml.
I have impression that another limitation might be its limitation in terms of functionality. I can't substantiate this impression yet. On 7/30/07, kumar k <[EMAIL PROTECTED]> wrote: > > I am a beginner. I see some of examples have servicemix.xml where as some > of examples have pom.xml. Servicemix.xml is called static configuration. > Why it is called so? What are the limitations of using servicemix.xml? > Thanx > Kumar > > > --------------------------------- > Get the free Yahoo! toolbar and rest assured with the added security of > spyware protection. -- Simon S.
