Thanks a lot!! I've been checking that page and now I understand there are two choices for configuring ServiceMix. The static one and the JBI packaging. Technically is clear, however... when would I use a static configuration or a JBI package? Which are the "best practices" for each configuration?
Just another question. Do you know why sometimes a SU contains the xbean.xml file and other times there is a servicemix.xml file instead ? Which is the exact utility for each file and when do I need to use one or another? Which is the functional difference between the servicemix.xml file in the root project and a servicemix.xml file in a service unit ? Thanks again in advance!! Antonio. gnodet wrote: > > These are different options that can be used with ServiceMix. > You can use a single static servicemix.xml configuration file or > use the standard JBI deployment (with components / SA / SU). > Then you can leverage our maven plugin or use ant. > > See also http://servicemix.goopen.org/site/4-examples.html > > On 11/6/06, AntonioPE <[EMAIL PROTECTED]> wrote: >> >> Hi all, >> >> I'm checking the examples that comes with the ServiceMix 3.0 in order to >> have a clear idea of which are the possibilities of the product, then >> I've >> found some points I do not understand very well. >> >> 1.- The example "file-binding" comes with just the servicemix.xml file in >> the project root folder. In this file there is the configuration of the >> filepoller and the filewriter components. And THAT's ALL ServiceMix needs >> to >> work (there's even no need to install any component in the ./components >> folder). >> >> 2.- The example "basic" comes with a maven structure (there is a pom.xml >> file) and in the ./src/main/resources all you have is a servicemix.xml >> file. >> Why is there just a servicemix.xml file in the "file-binding" example >> while >> here you have a maven structure ??? In any case in this servicemix.xml >> file >> there is all the configuration for all the components. >> >> 3.- In the example "bridge" you have a whole maven structure with >> different >> service units (bridge-eip-su, bridge-http-su, bridge-jms-su,...). For >> some >> of those SU you have a xbean.xml (*-eip-su, *-http-su, *-jms-su) file >> while >> for other you have a servicemix.xml file (*-xslt-su)... why?? why there's >> no >> a servicemix.xml file in the project root like it is in the >> "file-binding" ? >> >> My doubts are, why sometimes you just need a servicemix.xml file to put >> all >> the components and sometimes you need several files ? Why there are such >> differences in the ServiceMix's examples?? Why the "file-binding" example >> does not follow the maven structure?? >> >> Can any of you help me with this questions? >> Thanks!! >> >> >> -- >> View this message in context: >> http://www.nabble.com/Trying-to-understand-ServiceMix-tf2583139s12049.html#a7201043 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > > -- View this message in context: http://www.nabble.com/Trying-to-understand-ServiceMix-tf2583139s12049.html#a7214863 Sent from the ServiceMix - User mailing list archive at Nabble.com.
