Page History

...

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 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: If you look at the servicemix.xml file you will see it is strictly being used to configure the ServiceMix jbi container. In the lightweight container deployment,

We will not be editing this file for this type of deployment. It is not recommended to edit the servicemix.xml except for testing purposes or if you are creating an embedded ServiceMix configuration.

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/building the code, two 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.

...