On 7/30/07, Simon Sekat <[EMAIL PROTECTED]> wrote: > 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?
The servicemix.xml file is used to configure the ServiceMix container as well as the old lightweight components. Long ago, the lightweight components used to be statically configured but this limitation has since been removed. The pom.xml file is used to configure Maven as the project management tool. Please see the Maven documentation at http://maven.apache.org/ as well as the execellent Maven book at http://sonatype.com/book/index.html for more information on Maven. Bruce -- perl -e 'print unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' Apache ActiveMQ - http://activemq.org/ Apache ServiceMix - http://servicemix.org/ Apache Geronimo - http://geronimo.apache.org/ Castor - http://castor.org/
