JBI components, by themselves, can act as JBI containers. Adding more artifacts to installed components is called deployment. ServiceMix supports two modes of deployment—standard and JBI complaint, and lightweight.
Using this mode, we can install components at run time and deploy SAs onto them. These components are JBI specification compliant and hence they are JBI containers for other components too. They can accept SA deployments and are implemented using the servicemix-common module. Since they are JBI compliant, they are packaged as ZIP archive files with a jbi.xml descriptor.
Examples of a few ServiceMix standard JBI components are shown in the following list:
servicemix-jsr181servicemix-droolsservicemix-httpservicemix-jms
We can also configure the above mentioned standard components, to be used in a static deployment mode using the servicemix.xml configuration file.
We can deploy lightweight components in this mode. To do that...