Re: Problem using JmsCompoment with Tibco implementation

2016-02-02 Thread jacobnebu
It is working for me with JMS 2.0. update pom.xml file with exclude for jms 1.1 in camel-jms and add dependency for jms 2.o -- View this message in context: http://camel.465427.n5.nabble.com/Problem-using-JmsCompoment-with-Tibco-implementation-tp5059096p5777169.html Sent from the Camel - User

Re: Problem using JmsCompoment with Tibco implementation

2011-12-15 Thread Pierre HARDY
I did solve the problem. It was an API mismatch problem but not only. I don't know how Karaf (the OSGi container i'm using) works exactly regarding the classloaders but i suspect that placing the tibjms.jar in the lib fodler of Karaf prevents the jar's classes to load the interface from camel-jms

Re: Problem using JmsCompoment with Tibco implementation

2011-12-14 Thread Christian Schneider
Which jms api bundle do you use? Can you try to install the jms api jar from geronimo? in karaf: install mvn:org.apache.geronimo.specs/geronimo-jms_1.1_spec/1.1.1 Christian Am 13.12.2011 16:57, schrieb Pierre HARDY: I did the test and running a standalone camel works. I do not have the error

Re: Problem using JmsCompoment with Tibco implementation

2011-12-13 Thread Pierre HARDY
I did the test and running a standalone camel works. I do not have the error anymore. When i'm not providing the JMS API i have a classNotFoundException. Can it still be a double API missmatch ? Do you have ideas or lead to help me fix this problem ? Le 09/12/2011 10:38, Pierre HARDY a écrit : >

Re: Problem using JmsCompoment with Tibco implementation

2011-12-09 Thread Pierre HARDY
Actualy i'm providing a jms.jar (version 1.1) but i'm not sure of the compliance of ibjms jar, looking inside this jar didn't provide enought information but by comparing the API they look like the same. Christian, as you mention, i'm effectively using an OSGi container (Karaf) but i didn't find a

Re: Problem using JmsCompoment with Tibco implementation

2011-12-08 Thread Christian Schneider
I rather think there might be two different jms apis around. If the tibco impl and your bundle see different jms api classes then this error can happen. You can easily check Babaks assumption by running the same route outside OSGi. If it works outside OSGi than it is rather the double jms api

Re: Problem using JmsCompoment with Tibco implementation

2011-12-08 Thread bvahdat
Hi, could it be that the 'com.tibco.tibjms.TibjmsConnectionFactory' class you've got on the classpath is just JMS 1.0.2 and not necessarily JMS 1.1 complaint. Can you please check it, maybe through the Manifest inside the jar containing that class? >From Camel 2.5 onwards the support for the JMS