On 11/30/10 3:29 AM, klausb wrote:
While coding with Karaf and Camel 2.5.0, I made the following observation:
If I'm loading two communicating bundles using the VM endpoint I do not see
any problems.
Both get started and exchange messages as expected.
Afterwards, if I quit Karaf (^D) gracefully and restart it, Karaf wants
reloads the bundles from its cache to reach the state before the shutdown.
Here I see the NoTypeConversionAvailableException on one of the two bundles.
And it is always complaining about:
No type converter available to convert from type: java.lang.String to the
required type: java.lang.Boolean with value false
If you want to make sure Camel works well with the OSGi, you need to
make sure the camel-core and camel-spring bundle are started rightly
before the you application bundle is loaded.
The affected bundle consequently fails and does not start.
Is this known bug or do I need to prepare the container differently to avoid
this behavior?
What's the version of Karaf are you using ?
If you are using Karaf 2.1.0, you can specify the bundle's start level
from the features file.e
klaus.
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
