Hi, I'm deploying Camel as an OSGI bundle (part of an EBA) on Websphere using the Spring OSGI extender. When the bundle is started, the camelContext is started and the route is up and running.
I did notice however that it is not detecting that it is running in an OSGI environment and as such is not using the OsgiSpringCamelContext. This results in issues like TypeConverter package scanning not working in the OSGI container. Camel requires that the camel-spring bundle is STARTED before any bundles are started containing camel routes. What is the preferred way of dealing with this start-order dependency ? -- View this message in context: http://camel.465427.n5.nabble.com/Camel-as-an-OSGI-bundle-OSGI-detection-strategy-tp5722787.html Sent from the Camel - Users mailing list archive at Nabble.com.
