e that's a condition
specific to Osgi, it seems like the responsibility for tracking
TypeConverterLoader should be in camel-core-osgi. Perhaps tracked by,
yes, an OsgiDefaultCamelContextFactory service.
Though this raises an interesting question: Given TypeConverterLoader
is active, sho
finished loading.
If you are setting your application system level great then the
camel-core, you may work around that kind of issue.
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 instanc
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
