[jira] Created: (CAMEL-100) Most recent snapshot requires ActiveMQ

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (CAMEL-100) Most recent snapshot requires ActiveMQ

JIRA jira@apache.org
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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (CAMEL-100) Most recent snapshot requires ActiveMQ

JIRA jira@apache.org

    [ https://issues.apache.org/activemq/browse/CAMEL-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39921 ]

James Strachan commented on CAMEL-100:
--------------------------------------

Any idea how to reproduce the ClassNotFoundException? e.g. the camel-core project doesn't use activemq yet it uses the AnnotationTypeConverterLoader OK?

> 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (CAMEL-100) Most recent snapshot requires ActiveMQ

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/activemq/browse/CAMEL-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39922 ]

Aaron Crickenberger commented on CAMEL-100:
-------------------------------------------

In my case, I'm using these jars in a jboss deployment.  So long as I include each individual camel jar except camel-activemq, things are OK.

Add camel-activemq to camel-spring's pom.xml, and the run "mvn test" for camel-spring.  I couldn't get this to reproduce for camel-core for some reason.    I apologize that this isn't the most direct example, but the stack trace looks the same.

> 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (CAMEL-100) Most recent snapshot requires ActiveMQ

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (CAMEL-100) Most recent snapshot requires ActiveMQ

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/activemq/browse/CAMEL-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40062 ]

James Strachan commented on CAMEL-100:
--------------------------------------

I've added a test case to try reproduce this issue...

https://svn.apache.org/repos/asf/activemq/camel/trunk/tests/camel-partial-classpath-test/

am using a custom type converter, adding camel-activemq to the classpath but (AFAIK) without ActiveMQ and its working without any errors.

Maybe this has been fixed; or maybe I'm just not doing the right thing to reproduce your issue? Any ideas how to reproduce it? e.g. an example classpath that causes problems maybe?

> 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (CAMEL-100) Most recent snapshot requires ActiveMQ

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/activemq/browse/CAMEL-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Strachan resolved CAMEL-100.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.0

I figured out how to make this test case actually fail in the end; then added a fix for it.

> 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
>             Fix For: 1.2.0
>
>
> 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (CAMEL-100) Most recent snapshot requires ActiveMQ

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/activemq/browse/CAMEL-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40066 ]

Aaron Crickenberger commented on CAMEL-100:
-------------------------------------------

Nice work!  Out of curiosity, what was it that finally made the test case fail?  I couldn't quite discern from the svn commits.

> 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
>             Fix For: 1.2.0
>
>
> 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (CAMEL-100) Most recent snapshot requires ActiveMQ

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/activemq/browse/CAMEL-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40067 ]

James Strachan commented on CAMEL-100:
--------------------------------------

Am not 100% sure :) I added a custom converter to the test case, which certainly helped; then the test didn't fail in my IDE, but definitely failed in maven (i'd maybe not ran the test in maven when I thought it wasn't failing). It could have been not failing in my IDEA due to a bad classpath (e.g. an ActiveMQ jar on the classpath etc)

> 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
>             Fix For: 1.2.0
>
>
> 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.