Hi Gary,
thanks for the explanations. Gladly the issue with camel 2.18 did not
require to remove the dynamic import.
I still would like to remove the Dynamic Import but it would require a
lot of work on activemq. I did a similar thing for artemis already. I am
not sure though how well this t
my understanding is that it is related to embedding a broker and using
something like the jdbc store that uses a third party driver. The required
package import cannot be known in-advance.
Another scenario would be a custom broker plugin.
In essence, because there are extension points exposed by th
I have a problem with the acticemq camel component.
See https://issues.apache.org/jira/browse/AMQ-6597
I think it is related to the use of DynamicImport-Package: * in activemq
osgi.
We had a similar issue before. In the former case activemq or artemis
was searching for extensions and was tryi
