I was able to build an app with OsgiDefaultCamelContext, but I had to add a ServiceTracker to wait for org.apache.camel.spi.TypeConverterLoader to be registered. Before I did that, my bundles were trying to create SEDA queues before camel-core had finished loading.
If camel-core-osgi is going to be split into a separate bundle in 2.8, I'd like to suggest adding a couple things: - A service that supplies instances of OsgiDefaultCamelContext on demand. This gives applications a service to track before attempting camel operations. - An activator that does whatever service/bundle tracking is needed before registering the service. This isolates applications from camel-core workings. Thanks... Don
