You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Ron Smith <ro...@gmail.com> on 2010/07/19 21:33:37 UTC
latformTransactionManager not found in 2.4.0
After moving from camel 2.3.0 to 2.4.0 I am getting the error:
java.lang.ClassNotFoundException:
org.springframework.transaction.PlatformTransactionManager
when I execute:
context.addComponent("myjms",
JmsComponent.jmsComponentAutoAcknowledge(topicConnectionFactory));
I am including every JAR in the lib directory including the optional ones.
This is code that was working in 2.3.0.
Re: latformTransactionManager not found in 2.4.0
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I have created a ticket
https://issues.apache.org/activemq/browse/CAMEL-2974
To include the missing new jars provided in spring 3.0.x which we
missed when upgrading.
I will move the jdk 1.5 jars into a lib/jdk15 folder so they wont be
in the main lib folder.
Then you only got the core jars needed.
And there is a lib/spring with all the needed spring jars
On Tue, Jul 20, 2010 at 3:21 PM, Ron Smith
<ro...@valkyresoftware.com> wrote:
> I am really not trying to be difficult, I promise (imagine if I were :-) )
>
> So, there are Spring JARs that are now required for camel 2.4.0 but are not
> included in the binary distribution because the new version of Sping, has
> additional dependencies that only get sorted out if you choose to use maven?
>
> I don't mean to start another thread complaining about the dependency on
> maven (though I tend to agree), I see there are already plenty of those. My
> intent is to suggest that if Camel is intended to be its own framework and
> not just a bag on the side of Spring, the binary distribution of Camel
> should contain the jars required to run Camel and not just enough to get it
> to compile.
>
> Luckily, I guess, I get to use Java 6 so there are fewer of these issues.
>
> On Tue, Jul 20, 2010 at 2:17 AM, Willem Jiang <wi...@gmail.com>wrote:
>
>> Hi,
>>
>> Here are the dependencies jars when you are using JDK 1.6.x
>>
>> [INFO] The following files have been resolved:
>> [INFO] aopalliance:aopalliance:jar:1.0:compile
>> [INFO] org.apache.camel:camel-core:jar:2.5-SNAPSHOT:compile
>> [INFO] org.apache.camel:camel-spring:jar:2.5-SNAPSHOT:compile
>> [INFO] org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.1.1:compile
>> [INFO] org.fusesource.commonman:commons-management:jar:1.0:compile
>> [INFO] org.springframework:spring-aop:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework:spring-asm:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework:spring-beans:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework:spring-context:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework:spring-core:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework:spring-expression:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework:spring-jms:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework:spring-test:jar:3.0.3.RELEASE:test
>> [INFO] org.springframework:spring-tx:jar:3.0.3.RELEASE:compile
>>
>>
>> Willem
>>
>>
>> Claus Ibsen wrote:
>>
>>> Hi
>>>
>>> As told on another thread. camel-jms leverages spring-jms and
>>> therefore you need all the spring jars that spring-jms requires.
>>> The maven pom.xml file will help you.
>>>
>>> You need all the *compile* jars, the spec jars is optional (eg the JMS
>>> API, JTA API etc.)
>>> And since this is from JDK 1.5 there are some XML jars you dont need
>>> on Java 1.6 as they are provided out of the box.
>>>
>>>
>>> [INFO] Building Camel :: JMS
>>> [INFO] task-segment: [dependency:list]
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] [dependency:list]
>>> [INFO]
>>> [INFO] The following files have been resolved:
>>> [INFO] aopalliance:aopalliance:jar:1.0:compile
>>> [INFO] com.sun.xml.bind:jaxb-impl:jar:2.1.13:compile
>>> [INFO] commons-logging:commons-logging:jar:1.1.1:test
>>> [INFO] commons-logging:commons-logging-api:jar:1.1:compile
>>> [INFO] commons-net:commons-net:jar:2.0:test
>>> [INFO] commons-pool:commons-pool:jar:1.5.4:test
>>> [INFO] javax.activation:activation:jar:1.1:compile
>>> [INFO] javax.annotation:jsr250-api:jar:1.0:test
>>> [INFO] javax.xml.bind:jaxb-api:jar:2.1:compile
>>> [INFO] javax.xml.stream:stax-api:jar:1.0-2:compile
>>> [INFO] junit:junit:jar:4.8.1:test
>>> [INFO] log4j:log4j:jar:1.2.16:test
>>> [INFO] org.apache.activemq:activeio-core:jar:3.1.2:test
>>> [INFO] org.apache.activemq:activemq-camel:jar:5.3.2:test
>>> [INFO] org.apache.activemq:activemq-core:jar:5.3.2:test
>>> [INFO] org.apache.activemq:activemq-pool:jar:5.3.2:test
>>> [INFO] org.apache.activemq:kahadb:jar:5.3.2:test
>>> [INFO] org.apache.activemq.protobuf:activemq-protobuf:jar:1.0:test
>>> [INFO] org.apache.camel:camel-core:jar:2.5-SNAPSHOT:compile
>>> [INFO] org.apache.camel:camel-core:test-jar:tests:2.5-SNAPSHOT:test
>>> [INFO] org.apache.camel:camel-spring:jar:2.5-SNAPSHOT:compile
>>> [INFO] org.apache.camel:camel-spring:test-jar:tests:2.5-SNAPSHOT:test
>>> [INFO] org.apache.camel:camel-test:jar:2.5-SNAPSHOT:test
>>> [INFO]
>>> org.apache.geronimo.specs:geronimo-j2ee-management_1.0_spec:jar:1.1:test
>>> [INFO]
>>> org.apache.geronimo.specs:geronimo-j2ee-management_1.1_spec:jar:1.0.1:test
>>> [INFO]
>>> org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.1.1:compile
>>> [INFO]
>>> org.apache.geronimo.specs:geronimo-jta_1.0.1B_spec:jar:1.0.1:test
>>> [INFO] org.apache.xbean:xbean-spring:jar:3.5:test
>>> [INFO] org.fusesource.commonman:commons-management:jar:1.0:compile
>>> [INFO] org.jencks:jencks-amqpool:jar:2.2:test
>>> [INFO] org.osgi:org.osgi.core:jar:4.1.0:test
>>> [INFO] org.springframework:spring-aop:jar:3.0.3.RELEASE:compile
>>> [INFO] org.springframework:spring-asm:jar:3.0.3.RELEASE:compile
>>> [INFO] org.springframework:spring-beans:jar:3.0.3.RELEASE:compile
>>> [INFO] org.springframework:spring-context:jar:3.0.3.RELEASE:compile
>>> [INFO] org.springframework:spring-core:jar:3.0.3.RELEASE:compile
>>> [INFO] org.springframework:spring-expression:jar:3.0.3.RELEASE:compile
>>> [INFO] org.springframework:spring-jms:jar:3.0.3.RELEASE:compile
>>> [INFO] org.springframework:spring-test:jar:3.0.3.RELEASE:test
>>> [INFO] org.springframework:spring-tx:jar:3.0.3.RELEASE:compile
>>> [INFO] org.springframework.osgi:spring-osgi-core:jar:1.2.0:test
>>> [INFO] org.springframework.osgi:spring-osgi-io:jar:1.2.0:test
>>> [INFO]
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>>
>>> On Tue, Jul 20, 2010 at 5:44 AM, Ron Smith <ro...@gmail.com> wrote:
>>>
>>>> I have just extracted a minimal example which demonstrates the issue:
>>>>
>>>> import org.apache.camel.CamelContext;
>>>> import org.apache.camel.component.jms.JmsComponent;
>>>> import org.apache.camel.impl.DefaultCamelContext;
>>>>
>>>> import javax.jms.TopicConnectionFactory;
>>>> import javax.naming.Context;
>>>> import javax.naming.InitialContext;
>>>> import java.util.Hashtable;
>>>>
>>>> public class DemonstrateBug {
>>>>
>>>> public static void main(String[] args) throws Exception {
>>>> final CamelContext context = new DefaultCamelContext();
>>>> final Hashtable<String,String> env = new
>>>> Hashtable<String,String>();
>>>> env.put(Context.INITIAL_CONTEXT_FACTORY,
>>>> "com.tibco.tibjms.naming.TibjmsInitialContextFactory");
>>>> env.put(Context.PROVIDER_URL, "tcp://myjmsserver:65000");
>>>> env.put(Context.SECURITY_PRINCIPAL, "myprincipal");
>>>> env.put(Context.SECURITY_CREDENTIALS, "mycredentials");
>>>> final Context jndiContext = new InitialContext(env);
>>>> final TopicConnectionFactory topicConnectionFactory =
>>>> (TopicConnectionFactory)
>>>> jndiContext.lookup("mytopicfactory");
>>>>
>>>> context.addComponent("tibco",
>>>>
>>>> JmsComponent.jmsComponentAutoAcknowledge(topicConnectionFactory));
>>>> }
>>>> }
>>>>
>>>>
>>>> Compile this class with everything from the camel 2.4.0 lib directory
>>>> (including the optional stuff) plus tibjms.jar, ojdbc14.jar and
>>>> junit-4.4.jar (these are the same versions of the same jars I am using
>>>> with
>>>> 2.3.0 which don't contain any reference to Spring classes or jars). The
>>>> last line of code throws:
>>>>
>>>> Exception in thread "main" java.lang.NoClassDefFoundError:
>>>> org/springframework/transaction/PlatformTransactionManager
>>>> at DemonstrateBug.main(DemonstrateBug.java:22)
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Jul 19, 2010 at 10:20 PM, Ron Smith <ro...@gmail.com>
>>>> wrote:
>>>>
>>>> I just double checked my classpath and rebuilt everything from scratch.
>>>>> Definitely nothing from Spring 2.x included.
>>>>>
>>>>>
>>>>> On Mon, Jul 19, 2010 at 8:52 PM, Willem Jiang <willem.jiang@gmail.com
>>>>> >wrote:
>>>>>
>>>>> Hi,
>>>>>>
>>>>>> Camel 2.4.0 uses Spring 3.0.3 by default, please make sure your class
>>>>>> path
>>>>>> doesn't have any Spring 2.x jars.
>>>>>>
>>>>>>
>>>>>> Willem
>>>>>> ----------------------------------
>>>>>> Apache Camel, Apache CXF committer
>>>>>> Open Source Integration http://www.fusesource.com
>>>>>> Blog http://willemjiang.blogspot.com
>>>>>> Tiwtter http://twitter.com/willemjiang
>>>>>>
>>>>>> Ron Smith wrote:
>>>>>>
>>>>>> After moving from camel 2.3.0 to 2.4.0 I am getting the error:
>>>>>>>
>>>>>>> java.lang.ClassNotFoundException:
>>>>>>> org.springframework.transaction.PlatformTransactionManager
>>>>>>>
>>>>>>> when I execute:
>>>>>>>
>>>>>>> context.addComponent("myjms",
>>>>>>> JmsComponent.jmsComponentAutoAcknowledge(topicConnectionFactory));
>>>>>>>
>>>>>>> I am including every JAR in the lib directory including the optional
>>>>>>> ones.
>>>>>>> This is code that was working in 2.3.0.
>>>>>>>
>>>>>>>
>>>>>>>
>>>
>>>
>>>
>>
>
--
Claus Ibsen
Apache Camel Committer
Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: latformTransactionManager not found in 2.4.0
Posted by James Strachan <ja...@gmail.com>.
On 20 July 2010 16:51, Ron Smith <ro...@valkyresoftware.com> wrote:
> I hadn't thought about it that way, James, but does that mean there needs to
> be some distinction between what is "core" functionality and what is
> "add-in" functionality?
There kinda already is :). camel-core.jar is the core :). That comes
with a bunch of components/endpoints. Everything else is pretty much a
new kind of endpoint/component (or language mostly).
> And, if we go that route, how do you manage the
> dependencies of each of the add-ins?
Each add-on has its dependencies clearly described in a pom.xml and in
the maven reports.
> I think Claus is on the right track by
> separating out the jars for spring and Java 5, etc into subdirectories under
> the lib. That way, they will be there if they are needed and the
> requirements becomes more a little more clear. It still doesn't specify
> which camel jars depend on which spring or other jars but, if someone (like
> myself) chooses (or is forced) not to use maven, then it is on their (my)
> head to resolve those dependencies. At least I have the definitive set of
> resources available to do the resolution.
We've gotten out of the habbit of generating the maven site - but it
describes the dependencies of each module in camel nicely...
http://camel.apache.org/maven/camel-2.2.0/camel-core/dependencies.html
you can also look inside the jar to see the pom.xml which describes them too.
You can also use other repos and websites too...
http://mvnrepository.com/artifact/org.apache.camel/camel-jms
e.g.
http://mvnrepository.com/artifact/org.apache.camel/camel-jms/2.4.0
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
Re: latformTransactionManager not found in 2.4.0
Posted by Ron Smith <ro...@valkyresoftware.com>.
I hadn't thought about it that way, James, but does that mean there needs to
be some distinction between what is "core" functionality and what is
"add-in" functionality? And, if we go that route, how do you manage the
dependencies of each of the add-ins? I think Claus is on the right track by
separating out the jars for spring and Java 5, etc into subdirectories under
the lib. That way, they will be there if they are needed and the
requirements becomes more a little more clear. It still doesn't specify
which camel jars depend on which spring or other jars but, if someone (like
myself) chooses (or is forced) not to use maven, then it is on their (my)
head to resolve those dependencies. At least I have the definitive set of
resources available to do the resolution.
On Tue, Jul 20, 2010 at 10:03 AM, James Strachan
<ja...@gmail.com>wrote:
> On 20 July 2010 14:21, Ron Smith <ro...@valkyresoftware.com> wrote:
> > I am really not trying to be difficult, I promise (imagine if I were :-)
> )
> >
> > So, there are Spring JARs that are now required for camel 2.4.0 but are
> not
> > included in the binary distribution because the new version of Sping, has
> > additional dependencies that only get sorted out if you choose to use
> maven?
> >
> > I don't mean to start another thread complaining about the dependency on
> > maven (though I tend to agree), I see there are already plenty of those.
> My
> > intent is to suggest that if Camel is intended to be its own framework
> and
> > not just a bag on the side of Spring, the binary distribution of Camel
> > should contain the jars required to run Camel and not just enough to get
> it
> > to compile.
>
> FWIW Camel itself isn't dependent on Spring - you don't need spring at
> all to run Camel and lots of its components.
>
> But there are quite a few components which do depend on Spring (such
> as camel-jms) so its probably worth including Spring as well - even
> though its not required for Camel per se.
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://fusesource.com/
>
Re: latformTransactionManager not found in 2.4.0
Posted by James Strachan <ja...@gmail.com>.
On 20 July 2010 14:21, Ron Smith <ro...@valkyresoftware.com> wrote:
> I am really not trying to be difficult, I promise (imagine if I were :-) )
>
> So, there are Spring JARs that are now required for camel 2.4.0 but are not
> included in the binary distribution because the new version of Sping, has
> additional dependencies that only get sorted out if you choose to use maven?
>
> I don't mean to start another thread complaining about the dependency on
> maven (though I tend to agree), I see there are already plenty of those. My
> intent is to suggest that if Camel is intended to be its own framework and
> not just a bag on the side of Spring, the binary distribution of Camel
> should contain the jars required to run Camel and not just enough to get it
> to compile.
FWIW Camel itself isn't dependent on Spring - you don't need spring at
all to run Camel and lots of its components.
But there are quite a few components which do depend on Spring (such
as camel-jms) so its probably worth including Spring as well - even
though its not required for Camel per se.
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
Re: latformTransactionManager not found in 2.4.0
Posted by Ron Smith <ro...@valkyresoftware.com>.
I am really not trying to be difficult, I promise (imagine if I were :-) )
So, there are Spring JARs that are now required for camel 2.4.0 but are not
included in the binary distribution because the new version of Sping, has
additional dependencies that only get sorted out if you choose to use maven?
I don't mean to start another thread complaining about the dependency on
maven (though I tend to agree), I see there are already plenty of those. My
intent is to suggest that if Camel is intended to be its own framework and
not just a bag on the side of Spring, the binary distribution of Camel
should contain the jars required to run Camel and not just enough to get it
to compile.
Luckily, I guess, I get to use Java 6 so there are fewer of these issues.
On Tue, Jul 20, 2010 at 2:17 AM, Willem Jiang <wi...@gmail.com>wrote:
> Hi,
>
> Here are the dependencies jars when you are using JDK 1.6.x
>
> [INFO] The following files have been resolved:
> [INFO] aopalliance:aopalliance:jar:1.0:compile
> [INFO] org.apache.camel:camel-core:jar:2.5-SNAPSHOT:compile
> [INFO] org.apache.camel:camel-spring:jar:2.5-SNAPSHOT:compile
> [INFO] org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.1.1:compile
> [INFO] org.fusesource.commonman:commons-management:jar:1.0:compile
> [INFO] org.springframework:spring-aop:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework:spring-asm:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework:spring-beans:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework:spring-context:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework:spring-core:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework:spring-expression:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework:spring-jms:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework:spring-test:jar:3.0.3.RELEASE:test
> [INFO] org.springframework:spring-tx:jar:3.0.3.RELEASE:compile
>
>
> Willem
>
>
> Claus Ibsen wrote:
>
>> Hi
>>
>> As told on another thread. camel-jms leverages spring-jms and
>> therefore you need all the spring jars that spring-jms requires.
>> The maven pom.xml file will help you.
>>
>> You need all the *compile* jars, the spec jars is optional (eg the JMS
>> API, JTA API etc.)
>> And since this is from JDK 1.5 there are some XML jars you dont need
>> on Java 1.6 as they are provided out of the box.
>>
>>
>> [INFO] Building Camel :: JMS
>> [INFO] task-segment: [dependency:list]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] [dependency:list]
>> [INFO]
>> [INFO] The following files have been resolved:
>> [INFO] aopalliance:aopalliance:jar:1.0:compile
>> [INFO] com.sun.xml.bind:jaxb-impl:jar:2.1.13:compile
>> [INFO] commons-logging:commons-logging:jar:1.1.1:test
>> [INFO] commons-logging:commons-logging-api:jar:1.1:compile
>> [INFO] commons-net:commons-net:jar:2.0:test
>> [INFO] commons-pool:commons-pool:jar:1.5.4:test
>> [INFO] javax.activation:activation:jar:1.1:compile
>> [INFO] javax.annotation:jsr250-api:jar:1.0:test
>> [INFO] javax.xml.bind:jaxb-api:jar:2.1:compile
>> [INFO] javax.xml.stream:stax-api:jar:1.0-2:compile
>> [INFO] junit:junit:jar:4.8.1:test
>> [INFO] log4j:log4j:jar:1.2.16:test
>> [INFO] org.apache.activemq:activeio-core:jar:3.1.2:test
>> [INFO] org.apache.activemq:activemq-camel:jar:5.3.2:test
>> [INFO] org.apache.activemq:activemq-core:jar:5.3.2:test
>> [INFO] org.apache.activemq:activemq-pool:jar:5.3.2:test
>> [INFO] org.apache.activemq:kahadb:jar:5.3.2:test
>> [INFO] org.apache.activemq.protobuf:activemq-protobuf:jar:1.0:test
>> [INFO] org.apache.camel:camel-core:jar:2.5-SNAPSHOT:compile
>> [INFO] org.apache.camel:camel-core:test-jar:tests:2.5-SNAPSHOT:test
>> [INFO] org.apache.camel:camel-spring:jar:2.5-SNAPSHOT:compile
>> [INFO] org.apache.camel:camel-spring:test-jar:tests:2.5-SNAPSHOT:test
>> [INFO] org.apache.camel:camel-test:jar:2.5-SNAPSHOT:test
>> [INFO]
>> org.apache.geronimo.specs:geronimo-j2ee-management_1.0_spec:jar:1.1:test
>> [INFO]
>> org.apache.geronimo.specs:geronimo-j2ee-management_1.1_spec:jar:1.0.1:test
>> [INFO]
>> org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.1.1:compile
>> [INFO]
>> org.apache.geronimo.specs:geronimo-jta_1.0.1B_spec:jar:1.0.1:test
>> [INFO] org.apache.xbean:xbean-spring:jar:3.5:test
>> [INFO] org.fusesource.commonman:commons-management:jar:1.0:compile
>> [INFO] org.jencks:jencks-amqpool:jar:2.2:test
>> [INFO] org.osgi:org.osgi.core:jar:4.1.0:test
>> [INFO] org.springframework:spring-aop:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework:spring-asm:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework:spring-beans:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework:spring-context:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework:spring-core:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework:spring-expression:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework:spring-jms:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework:spring-test:jar:3.0.3.RELEASE:test
>> [INFO] org.springframework:spring-tx:jar:3.0.3.RELEASE:compile
>> [INFO] org.springframework.osgi:spring-osgi-core:jar:1.2.0:test
>> [INFO] org.springframework.osgi:spring-osgi-io:jar:1.2.0:test
>> [INFO]
>> [INFO]
>> ------------------------------------------------------------------------
>>
>>
>> On Tue, Jul 20, 2010 at 5:44 AM, Ron Smith <ro...@gmail.com> wrote:
>>
>>> I have just extracted a minimal example which demonstrates the issue:
>>>
>>> import org.apache.camel.CamelContext;
>>> import org.apache.camel.component.jms.JmsComponent;
>>> import org.apache.camel.impl.DefaultCamelContext;
>>>
>>> import javax.jms.TopicConnectionFactory;
>>> import javax.naming.Context;
>>> import javax.naming.InitialContext;
>>> import java.util.Hashtable;
>>>
>>> public class DemonstrateBug {
>>>
>>> public static void main(String[] args) throws Exception {
>>> final CamelContext context = new DefaultCamelContext();
>>> final Hashtable<String,String> env = new
>>> Hashtable<String,String>();
>>> env.put(Context.INITIAL_CONTEXT_FACTORY,
>>> "com.tibco.tibjms.naming.TibjmsInitialContextFactory");
>>> env.put(Context.PROVIDER_URL, "tcp://myjmsserver:65000");
>>> env.put(Context.SECURITY_PRINCIPAL, "myprincipal");
>>> env.put(Context.SECURITY_CREDENTIALS, "mycredentials");
>>> final Context jndiContext = new InitialContext(env);
>>> final TopicConnectionFactory topicConnectionFactory =
>>> (TopicConnectionFactory)
>>> jndiContext.lookup("mytopicfactory");
>>>
>>> context.addComponent("tibco",
>>>
>>> JmsComponent.jmsComponentAutoAcknowledge(topicConnectionFactory));
>>> }
>>> }
>>>
>>>
>>> Compile this class with everything from the camel 2.4.0 lib directory
>>> (including the optional stuff) plus tibjms.jar, ojdbc14.jar and
>>> junit-4.4.jar (these are the same versions of the same jars I am using
>>> with
>>> 2.3.0 which don't contain any reference to Spring classes or jars). The
>>> last line of code throws:
>>>
>>> Exception in thread "main" java.lang.NoClassDefFoundError:
>>> org/springframework/transaction/PlatformTransactionManager
>>> at DemonstrateBug.main(DemonstrateBug.java:22)
>>>
>>>
>>>
>>>
>>> On Mon, Jul 19, 2010 at 10:20 PM, Ron Smith <ro...@gmail.com>
>>> wrote:
>>>
>>> I just double checked my classpath and rebuilt everything from scratch.
>>>> Definitely nothing from Spring 2.x included.
>>>>
>>>>
>>>> On Mon, Jul 19, 2010 at 8:52 PM, Willem Jiang <willem.jiang@gmail.com
>>>> >wrote:
>>>>
>>>> Hi,
>>>>>
>>>>> Camel 2.4.0 uses Spring 3.0.3 by default, please make sure your class
>>>>> path
>>>>> doesn't have any Spring 2.x jars.
>>>>>
>>>>>
>>>>> Willem
>>>>> ----------------------------------
>>>>> Apache Camel, Apache CXF committer
>>>>> Open Source Integration http://www.fusesource.com
>>>>> Blog http://willemjiang.blogspot.com
>>>>> Tiwtter http://twitter.com/willemjiang
>>>>>
>>>>> Ron Smith wrote:
>>>>>
>>>>> After moving from camel 2.3.0 to 2.4.0 I am getting the error:
>>>>>>
>>>>>> java.lang.ClassNotFoundException:
>>>>>> org.springframework.transaction.PlatformTransactionManager
>>>>>>
>>>>>> when I execute:
>>>>>>
>>>>>> context.addComponent("myjms",
>>>>>> JmsComponent.jmsComponentAutoAcknowledge(topicConnectionFactory));
>>>>>>
>>>>>> I am including every JAR in the lib directory including the optional
>>>>>> ones.
>>>>>> This is code that was working in 2.3.0.
>>>>>>
>>>>>>
>>>>>>
>>
>>
>>
>
Re: latformTransactionManager not found in 2.4.0
Posted by Willem Jiang <wi...@gmail.com>.
Hi,
Here are the dependencies jars when you are using JDK 1.6.x
[INFO] The following files have been resolved:
[INFO] aopalliance:aopalliance:jar:1.0:compile
[INFO] org.apache.camel:camel-core:jar:2.5-SNAPSHOT:compile
[INFO] org.apache.camel:camel-spring:jar:2.5-SNAPSHOT:compile
[INFO] org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.1.1:compile
[INFO] org.fusesource.commonman:commons-management:jar:1.0:compile
[INFO] org.springframework:spring-aop:jar:3.0.3.RELEASE:compile
[INFO] org.springframework:spring-asm:jar:3.0.3.RELEASE:compile
[INFO] org.springframework:spring-beans:jar:3.0.3.RELEASE:compile
[INFO] org.springframework:spring-context:jar:3.0.3.RELEASE:compile
[INFO] org.springframework:spring-core:jar:3.0.3.RELEASE:compile
[INFO] org.springframework:spring-expression:jar:3.0.3.RELEASE:compile
[INFO] org.springframework:spring-jms:jar:3.0.3.RELEASE:compile
[INFO] org.springframework:spring-test:jar:3.0.3.RELEASE:test
[INFO] org.springframework:spring-tx:jar:3.0.3.RELEASE:compile
Willem
Claus Ibsen wrote:
> Hi
>
> As told on another thread. camel-jms leverages spring-jms and
> therefore you need all the spring jars that spring-jms requires.
> The maven pom.xml file will help you.
>
> You need all the *compile* jars, the spec jars is optional (eg the JMS
> API, JTA API etc.)
> And since this is from JDK 1.5 there are some XML jars you dont need
> on Java 1.6 as they are provided out of the box.
>
>
> [INFO] Building Camel :: JMS
> [INFO] task-segment: [dependency:list]
> [INFO] ------------------------------------------------------------------------
> [INFO] [dependency:list]
> [INFO]
> [INFO] The following files have been resolved:
> [INFO] aopalliance:aopalliance:jar:1.0:compile
> [INFO] com.sun.xml.bind:jaxb-impl:jar:2.1.13:compile
> [INFO] commons-logging:commons-logging:jar:1.1.1:test
> [INFO] commons-logging:commons-logging-api:jar:1.1:compile
> [INFO] commons-net:commons-net:jar:2.0:test
> [INFO] commons-pool:commons-pool:jar:1.5.4:test
> [INFO] javax.activation:activation:jar:1.1:compile
> [INFO] javax.annotation:jsr250-api:jar:1.0:test
> [INFO] javax.xml.bind:jaxb-api:jar:2.1:compile
> [INFO] javax.xml.stream:stax-api:jar:1.0-2:compile
> [INFO] junit:junit:jar:4.8.1:test
> [INFO] log4j:log4j:jar:1.2.16:test
> [INFO] org.apache.activemq:activeio-core:jar:3.1.2:test
> [INFO] org.apache.activemq:activemq-camel:jar:5.3.2:test
> [INFO] org.apache.activemq:activemq-core:jar:5.3.2:test
> [INFO] org.apache.activemq:activemq-pool:jar:5.3.2:test
> [INFO] org.apache.activemq:kahadb:jar:5.3.2:test
> [INFO] org.apache.activemq.protobuf:activemq-protobuf:jar:1.0:test
> [INFO] org.apache.camel:camel-core:jar:2.5-SNAPSHOT:compile
> [INFO] org.apache.camel:camel-core:test-jar:tests:2.5-SNAPSHOT:test
> [INFO] org.apache.camel:camel-spring:jar:2.5-SNAPSHOT:compile
> [INFO] org.apache.camel:camel-spring:test-jar:tests:2.5-SNAPSHOT:test
> [INFO] org.apache.camel:camel-test:jar:2.5-SNAPSHOT:test
> [INFO] org.apache.geronimo.specs:geronimo-j2ee-management_1.0_spec:jar:1.1:test
> [INFO] org.apache.geronimo.specs:geronimo-j2ee-management_1.1_spec:jar:1.0.1:test
> [INFO] org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.1.1:compile
> [INFO] org.apache.geronimo.specs:geronimo-jta_1.0.1B_spec:jar:1.0.1:test
> [INFO] org.apache.xbean:xbean-spring:jar:3.5:test
> [INFO] org.fusesource.commonman:commons-management:jar:1.0:compile
> [INFO] org.jencks:jencks-amqpool:jar:2.2:test
> [INFO] org.osgi:org.osgi.core:jar:4.1.0:test
> [INFO] org.springframework:spring-aop:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework:spring-asm:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework:spring-beans:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework:spring-context:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework:spring-core:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework:spring-expression:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework:spring-jms:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework:spring-test:jar:3.0.3.RELEASE:test
> [INFO] org.springframework:spring-tx:jar:3.0.3.RELEASE:compile
> [INFO] org.springframework.osgi:spring-osgi-core:jar:1.2.0:test
> [INFO] org.springframework.osgi:spring-osgi-io:jar:1.2.0:test
> [INFO]
> [INFO] ------------------------------------------------------------------------
>
>
> On Tue, Jul 20, 2010 at 5:44 AM, Ron Smith <ro...@gmail.com> wrote:
>> I have just extracted a minimal example which demonstrates the issue:
>>
>> import org.apache.camel.CamelContext;
>> import org.apache.camel.component.jms.JmsComponent;
>> import org.apache.camel.impl.DefaultCamelContext;
>>
>> import javax.jms.TopicConnectionFactory;
>> import javax.naming.Context;
>> import javax.naming.InitialContext;
>> import java.util.Hashtable;
>>
>> public class DemonstrateBug {
>>
>> public static void main(String[] args) throws Exception {
>> final CamelContext context = new DefaultCamelContext();
>> final Hashtable<String,String> env = new Hashtable<String,String>();
>> env.put(Context.INITIAL_CONTEXT_FACTORY,
>> "com.tibco.tibjms.naming.TibjmsInitialContextFactory");
>> env.put(Context.PROVIDER_URL, "tcp://myjmsserver:65000");
>> env.put(Context.SECURITY_PRINCIPAL, "myprincipal");
>> env.put(Context.SECURITY_CREDENTIALS, "mycredentials");
>> final Context jndiContext = new InitialContext(env);
>> final TopicConnectionFactory topicConnectionFactory =
>> (TopicConnectionFactory)
>> jndiContext.lookup("mytopicfactory");
>>
>> context.addComponent("tibco",
>>
>> JmsComponent.jmsComponentAutoAcknowledge(topicConnectionFactory));
>> }
>> }
>>
>>
>> Compile this class with everything from the camel 2.4.0 lib directory
>> (including the optional stuff) plus tibjms.jar, ojdbc14.jar and
>> junit-4.4.jar (these are the same versions of the same jars I am using with
>> 2.3.0 which don't contain any reference to Spring classes or jars). The
>> last line of code throws:
>>
>> Exception in thread "main" java.lang.NoClassDefFoundError:
>> org/springframework/transaction/PlatformTransactionManager
>> at DemonstrateBug.main(DemonstrateBug.java:22)
>>
>>
>>
>>
>> On Mon, Jul 19, 2010 at 10:20 PM, Ron Smith <ro...@gmail.com> wrote:
>>
>>> I just double checked my classpath and rebuilt everything from scratch.
>>> Definitely nothing from Spring 2.x included.
>>>
>>>
>>> On Mon, Jul 19, 2010 at 8:52 PM, Willem Jiang <wi...@gmail.com>wrote:
>>>
>>>> Hi,
>>>>
>>>> Camel 2.4.0 uses Spring 3.0.3 by default, please make sure your class path
>>>> doesn't have any Spring 2.x jars.
>>>>
>>>>
>>>> Willem
>>>> ----------------------------------
>>>> Apache Camel, Apache CXF committer
>>>> Open Source Integration http://www.fusesource.com
>>>> Blog http://willemjiang.blogspot.com
>>>> Tiwtter http://twitter.com/willemjiang
>>>>
>>>> Ron Smith wrote:
>>>>
>>>>> After moving from camel 2.3.0 to 2.4.0 I am getting the error:
>>>>>
>>>>> java.lang.ClassNotFoundException:
>>>>> org.springframework.transaction.PlatformTransactionManager
>>>>>
>>>>> when I execute:
>>>>>
>>>>> context.addComponent("myjms",
>>>>> JmsComponent.jmsComponentAutoAcknowledge(topicConnectionFactory));
>>>>>
>>>>> I am including every JAR in the lib directory including the optional
>>>>> ones.
>>>>> This is code that was working in 2.3.0.
>>>>>
>>>>>
>
>
>
Re: latformTransactionManager not found in 2.4.0
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
As told on another thread. camel-jms leverages spring-jms and
therefore you need all the spring jars that spring-jms requires.
The maven pom.xml file will help you.
You need all the *compile* jars, the spec jars is optional (eg the JMS
API, JTA API etc.)
And since this is from JDK 1.5 there are some XML jars you dont need
on Java 1.6 as they are provided out of the box.
[INFO] Building Camel :: JMS
[INFO] task-segment: [dependency:list]
[INFO] ------------------------------------------------------------------------
[INFO] [dependency:list]
[INFO]
[INFO] The following files have been resolved:
[INFO] aopalliance:aopalliance:jar:1.0:compile
[INFO] com.sun.xml.bind:jaxb-impl:jar:2.1.13:compile
[INFO] commons-logging:commons-logging:jar:1.1.1:test
[INFO] commons-logging:commons-logging-api:jar:1.1:compile
[INFO] commons-net:commons-net:jar:2.0:test
[INFO] commons-pool:commons-pool:jar:1.5.4:test
[INFO] javax.activation:activation:jar:1.1:compile
[INFO] javax.annotation:jsr250-api:jar:1.0:test
[INFO] javax.xml.bind:jaxb-api:jar:2.1:compile
[INFO] javax.xml.stream:stax-api:jar:1.0-2:compile
[INFO] junit:junit:jar:4.8.1:test
[INFO] log4j:log4j:jar:1.2.16:test
[INFO] org.apache.activemq:activeio-core:jar:3.1.2:test
[INFO] org.apache.activemq:activemq-camel:jar:5.3.2:test
[INFO] org.apache.activemq:activemq-core:jar:5.3.2:test
[INFO] org.apache.activemq:activemq-pool:jar:5.3.2:test
[INFO] org.apache.activemq:kahadb:jar:5.3.2:test
[INFO] org.apache.activemq.protobuf:activemq-protobuf:jar:1.0:test
[INFO] org.apache.camel:camel-core:jar:2.5-SNAPSHOT:compile
[INFO] org.apache.camel:camel-core:test-jar:tests:2.5-SNAPSHOT:test
[INFO] org.apache.camel:camel-spring:jar:2.5-SNAPSHOT:compile
[INFO] org.apache.camel:camel-spring:test-jar:tests:2.5-SNAPSHOT:test
[INFO] org.apache.camel:camel-test:jar:2.5-SNAPSHOT:test
[INFO] org.apache.geronimo.specs:geronimo-j2ee-management_1.0_spec:jar:1.1:test
[INFO] org.apache.geronimo.specs:geronimo-j2ee-management_1.1_spec:jar:1.0.1:test
[INFO] org.apache.geronimo.specs:geronimo-jms_1.1_spec:jar:1.1.1:compile
[INFO] org.apache.geronimo.specs:geronimo-jta_1.0.1B_spec:jar:1.0.1:test
[INFO] org.apache.xbean:xbean-spring:jar:3.5:test
[INFO] org.fusesource.commonman:commons-management:jar:1.0:compile
[INFO] org.jencks:jencks-amqpool:jar:2.2:test
[INFO] org.osgi:org.osgi.core:jar:4.1.0:test
[INFO] org.springframework:spring-aop:jar:3.0.3.RELEASE:compile
[INFO] org.springframework:spring-asm:jar:3.0.3.RELEASE:compile
[INFO] org.springframework:spring-beans:jar:3.0.3.RELEASE:compile
[INFO] org.springframework:spring-context:jar:3.0.3.RELEASE:compile
[INFO] org.springframework:spring-core:jar:3.0.3.RELEASE:compile
[INFO] org.springframework:spring-expression:jar:3.0.3.RELEASE:compile
[INFO] org.springframework:spring-jms:jar:3.0.3.RELEASE:compile
[INFO] org.springframework:spring-test:jar:3.0.3.RELEASE:test
[INFO] org.springframework:spring-tx:jar:3.0.3.RELEASE:compile
[INFO] org.springframework.osgi:spring-osgi-core:jar:1.2.0:test
[INFO] org.springframework.osgi:spring-osgi-io:jar:1.2.0:test
[INFO]
[INFO] ------------------------------------------------------------------------
On Tue, Jul 20, 2010 at 5:44 AM, Ron Smith <ro...@gmail.com> wrote:
> I have just extracted a minimal example which demonstrates the issue:
>
> import org.apache.camel.CamelContext;
> import org.apache.camel.component.jms.JmsComponent;
> import org.apache.camel.impl.DefaultCamelContext;
>
> import javax.jms.TopicConnectionFactory;
> import javax.naming.Context;
> import javax.naming.InitialContext;
> import java.util.Hashtable;
>
> public class DemonstrateBug {
>
> public static void main(String[] args) throws Exception {
> final CamelContext context = new DefaultCamelContext();
> final Hashtable<String,String> env = new Hashtable<String,String>();
> env.put(Context.INITIAL_CONTEXT_FACTORY,
> "com.tibco.tibjms.naming.TibjmsInitialContextFactory");
> env.put(Context.PROVIDER_URL, "tcp://myjmsserver:65000");
> env.put(Context.SECURITY_PRINCIPAL, "myprincipal");
> env.put(Context.SECURITY_CREDENTIALS, "mycredentials");
> final Context jndiContext = new InitialContext(env);
> final TopicConnectionFactory topicConnectionFactory =
> (TopicConnectionFactory)
> jndiContext.lookup("mytopicfactory");
>
> context.addComponent("tibco",
>
> JmsComponent.jmsComponentAutoAcknowledge(topicConnectionFactory));
> }
> }
>
>
> Compile this class with everything from the camel 2.4.0 lib directory
> (including the optional stuff) plus tibjms.jar, ojdbc14.jar and
> junit-4.4.jar (these are the same versions of the same jars I am using with
> 2.3.0 which don't contain any reference to Spring classes or jars). The
> last line of code throws:
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/springframework/transaction/PlatformTransactionManager
> at DemonstrateBug.main(DemonstrateBug.java:22)
>
>
>
>
> On Mon, Jul 19, 2010 at 10:20 PM, Ron Smith <ro...@gmail.com> wrote:
>
>> I just double checked my classpath and rebuilt everything from scratch.
>> Definitely nothing from Spring 2.x included.
>>
>>
>> On Mon, Jul 19, 2010 at 8:52 PM, Willem Jiang <wi...@gmail.com>wrote:
>>
>>> Hi,
>>>
>>> Camel 2.4.0 uses Spring 3.0.3 by default, please make sure your class path
>>> doesn't have any Spring 2.x jars.
>>>
>>>
>>> Willem
>>> ----------------------------------
>>> Apache Camel, Apache CXF committer
>>> Open Source Integration http://www.fusesource.com
>>> Blog http://willemjiang.blogspot.com
>>> Tiwtter http://twitter.com/willemjiang
>>>
>>> Ron Smith wrote:
>>>
>>>> After moving from camel 2.3.0 to 2.4.0 I am getting the error:
>>>>
>>>> java.lang.ClassNotFoundException:
>>>> org.springframework.transaction.PlatformTransactionManager
>>>>
>>>> when I execute:
>>>>
>>>> context.addComponent("myjms",
>>>> JmsComponent.jmsComponentAutoAcknowledge(topicConnectionFactory));
>>>>
>>>> I am including every JAR in the lib directory including the optional
>>>> ones.
>>>> This is code that was working in 2.3.0.
>>>>
>>>>
>>>
>>
>
--
Claus Ibsen
Apache Camel Committer
Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: latformTransactionManager not found in 2.4.0
Posted by Ron Smith <ro...@gmail.com>.
I have just extracted a minimal example which demonstrates the issue:
import org.apache.camel.CamelContext;
import org.apache.camel.component.jms.JmsComponent;
import org.apache.camel.impl.DefaultCamelContext;
import javax.jms.TopicConnectionFactory;
import javax.naming.Context;
import javax.naming.InitialContext;
import java.util.Hashtable;
public class DemonstrateBug {
public static void main(String[] args) throws Exception {
final CamelContext context = new DefaultCamelContext();
final Hashtable<String,String> env = new Hashtable<String,String>();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.tibco.tibjms.naming.TibjmsInitialContextFactory");
env.put(Context.PROVIDER_URL, "tcp://myjmsserver:65000");
env.put(Context.SECURITY_PRINCIPAL, "myprincipal");
env.put(Context.SECURITY_CREDENTIALS, "mycredentials");
final Context jndiContext = new InitialContext(env);
final TopicConnectionFactory topicConnectionFactory =
(TopicConnectionFactory)
jndiContext.lookup("mytopicfactory");
context.addComponent("tibco",
JmsComponent.jmsComponentAutoAcknowledge(topicConnectionFactory));
}
}
Compile this class with everything from the camel 2.4.0 lib directory
(including the optional stuff) plus tibjms.jar, ojdbc14.jar and
junit-4.4.jar (these are the same versions of the same jars I am using with
2.3.0 which don't contain any reference to Spring classes or jars). The
last line of code throws:
Exception in thread "main" java.lang.NoClassDefFoundError:
org/springframework/transaction/PlatformTransactionManager
at DemonstrateBug.main(DemonstrateBug.java:22)
On Mon, Jul 19, 2010 at 10:20 PM, Ron Smith <ro...@gmail.com> wrote:
> I just double checked my classpath and rebuilt everything from scratch.
> Definitely nothing from Spring 2.x included.
>
>
> On Mon, Jul 19, 2010 at 8:52 PM, Willem Jiang <wi...@gmail.com>wrote:
>
>> Hi,
>>
>> Camel 2.4.0 uses Spring 3.0.3 by default, please make sure your class path
>> doesn't have any Spring 2.x jars.
>>
>>
>> Willem
>> ----------------------------------
>> Apache Camel, Apache CXF committer
>> Open Source Integration http://www.fusesource.com
>> Blog http://willemjiang.blogspot.com
>> Tiwtter http://twitter.com/willemjiang
>>
>> Ron Smith wrote:
>>
>>> After moving from camel 2.3.0 to 2.4.0 I am getting the error:
>>>
>>> java.lang.ClassNotFoundException:
>>> org.springframework.transaction.PlatformTransactionManager
>>>
>>> when I execute:
>>>
>>> context.addComponent("myjms",
>>> JmsComponent.jmsComponentAutoAcknowledge(topicConnectionFactory));
>>>
>>> I am including every JAR in the lib directory including the optional
>>> ones.
>>> This is code that was working in 2.3.0.
>>>
>>>
>>
>
Re: latformTransactionManager not found in 2.4.0
Posted by Ron Smith <ro...@gmail.com>.
I just double checked my classpath and rebuilt everything from scratch.
Definitely nothing from Spring 2.x included.
On Mon, Jul 19, 2010 at 8:52 PM, Willem Jiang <wi...@gmail.com>wrote:
> Hi,
>
> Camel 2.4.0 uses Spring 3.0.3 by default, please make sure your class path
> doesn't have any Spring 2.x jars.
>
>
> Willem
> ----------------------------------
> Apache Camel, Apache CXF committer
> Open Source Integration http://www.fusesource.com
> Blog http://willemjiang.blogspot.com
> Tiwtter http://twitter.com/willemjiang
>
> Ron Smith wrote:
>
>> After moving from camel 2.3.0 to 2.4.0 I am getting the error:
>>
>> java.lang.ClassNotFoundException:
>> org.springframework.transaction.PlatformTransactionManager
>>
>> when I execute:
>>
>> context.addComponent("myjms",
>> JmsComponent.jmsComponentAutoAcknowledge(topicConnectionFactory));
>>
>> I am including every JAR in the lib directory including the optional ones.
>> This is code that was working in 2.3.0.
>>
>>
>
Re: latformTransactionManager not found in 2.4.0
Posted by Willem Jiang <wi...@gmail.com>.
Hi,
Camel 2.4.0 uses Spring 3.0.3 by default, please make sure your class
path doesn't have any Spring 2.x jars.
Willem
----------------------------------
Apache Camel, Apache CXF committer
Open Source Integration http://www.fusesource.com
Blog http://willemjiang.blogspot.com
Tiwtter http://twitter.com/willemjiang
Ron Smith wrote:
> After moving from camel 2.3.0 to 2.4.0 I am getting the error:
>
> java.lang.ClassNotFoundException:
> org.springframework.transaction.PlatformTransactionManager
>
> when I execute:
>
> context.addComponent("myjms",
> JmsComponent.jmsComponentAutoAcknowledge(topicConnectionFactory));
>
> I am including every JAR in the lib directory including the optional ones.
> This is code that was working in 2.3.0.
>