[
https://issues.apache.org/activemq/browse/CAMEL-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39924
]
James Strachan commented on CAMEL-100:
--------------------------------------
Any chance of getting a stack trace to see exactly where this occurs?
BTW I think I get it now - Camel auto-discovers type converters in each
library. So if you add, say, camel-activemq.jar to the classpath but without
the activemq code, it won't be able to load the type converters defined in
camel-activemq.jar.
To fix this we should just log some kinda warning that the type converters in
camel-activemq cannot be used or something?
> Most recent snapshot requires ActiveMQ
> --------------------------------------
>
> Key: CAMEL-100
> URL: https://issues.apache.org/activemq/browse/CAMEL-100
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-activemq
> Affects Versions: 1.1.0
> Reporter: Aaron Crickenberger
> Priority: Minor
>
> This may be moot given the projects' relationship, but it's a recently
> introduced side effect. Before the most recent snapshot, I was able to use
> Camel without any ActiveMQ jar's floating around so long as I never tried to
> use any "activemq:queue:foo" URI's. Now with the most recent snapshot, the
> first time I do something that uses AnnotationTypeCoverterLoader,
> ActiveMQConverter gets loaded, and then causes a NoClassDefFoundError for
> ActiveMQDestination.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
