THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Remark: for more information about Spring Dynamic Modules and configuration, I recommend to read its documentation
| Tip | ||
|---|---|---|
| ||
Two XML files have been created to work with Spring beans and Spring OSGI beans separately (as proposed by spring - section D.1 Generated Project Features at-a-glance) but you can also merge the content in one file. |
Step 5 : Generate the MANIFEST.MF file and jar of the bundle
...
Run the command mvn package (= Repeat step #5).
Unfortunately, the MANIFEST.MF file of the Camel bundle does not contain a link to the package demo.Service that the bean 'myTransform' required in order to instantiate the class. This link is not added by the bnd tool during the generation step. So we have to edit the file contained in the jar file demo.camel-bundle-0.1.jar adding the following line at the end of the MANIFEST.MF file.
Remark: if someone find how to avoid this, he/she is welcome 
| Code Block |
|---|
Import-Package: demo.service
|
Save the MANIFEST.MF file (and the jar containing it)
Deploy the bundles
We will show you now that we can easily deploy our bundles in two OSGI servers running a different OSGI kernel:
...