THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Explain diff between std jbi component and lw component and the static use of ServiceMix.
See http://docs.codehaus.org/display/SM/What+is+a+lightweight+component
for a good explanation of the different types of JBI components.
Two main use cases for ServiceMix:
1. As a ull JBI container - using SMX as a full JBI container in which you can deploy Service Assemblies and standard JBI components. And you may also deploy lightweight components in this mode - they must be deployed to the servicemix-lwcontainer.
...
There are several things to note about this example. First of all it is meant to be run stand-alone. Specifically, when running this example, ServiceMix will be started for you, then the loan broker is
deployed and run. Therefore, there is a servicemix.xml file in the loan-broker directory. This
servicemix.xml file is used to configure for configuring the ServiceMix JBI container upon ServiceMix starting up. This is not to be confused with the servicemix.xml located in the loan-broker\src\su directory. The SU servicemix.xml file is used to configure the servicemix-lwcontainer. Every service unit must contain some kind of configuration file. For example, if we were creating a service unit for the BPEL service engine there would also be a configuration file, but it would not be a servicemix.xml file, such as the one used for configuring the lightweight container.
NOTE: There are two major phases to creating a lightweight component that is ready for deployment: one, is the development phase of the component, which includes coding and compiling /and building the code, two the second phase is creating the packaging necessary for the component to be installed onto the JBI container. This document will focus on the second part. Any steps relating to compilation are simply performed here to get us to the point that we can assemble the component into a JBI service assembly or service unit.
...
Now we are ready to assemble the components together. The loan broker demo supplies us with the build.xml file (which was used in the compile step above as well). The build.xml contains targets for creating service units. If you run "ant setup" all the service units will automatically be created. Ultimately, this is what you will want to do, however, the following procedure gives the manual steps for creating a service unit, to facilitate in understanding the contents of a service unit.
...