Hi Guillaume,
Before we did some hacking work to let camel load the converters from
all the bundles, we leverage the camel context OSGi bundle classloader
to find the converters. In old way, we can configure the which kind of
converter we want load by importing the converter's package in the camel
context OSGi bundle.
Now if we want to this feature back, we can revert the change or
introduce a new class filter mechanism to camel.
Willem
Guillaume Nodet wrote:
I just want to raise a potential problem with the way the camel
converters are discovered in OSGi.
The main problem i see is that this discovery is global: i.e. camel
will discover and use all converters from all installed bundles.
I think this could be a problem when you deploy multiple applications:
i.e. when you deploy a new application with a few new converters, this
could have side effects on another application, eventually breaking
it.
I wonder if we should have a more static way of configuring converters
for a given route.
Thoughts ?
