Re: [Carbon-dev] Problem using Qpid client libraries with JMS transport

2011-02-02 Thread Rajika Kumarasiri
I was able to get this fix by dropping the mina-core jar into the same location. Rajika On Tue, Feb 1, 2011 at 4:12 PM, Rajika Kumarasiri raj...@wso2.com wrote: I am having problems with using Qpid client libraries with JMS transport. I have dropped the required libraries(qpid-client-0.9.jar,

[Carbon-dev] Problem using Qpid client libraries with JMS transport

2011-02-01 Thread Rajika Kumarasiri
I am having problems with using Qpid client libraries with JMS transport. I have dropped the required libraries(qpid-client-0.9.jar, qpid-common-0.9.jar, slf4j-api-1.6.1.jar and slf4j-log4j12-1.6.1.jar) into $CARBON_HOME/lib/core/WEB-INF/lib and the following stack trace is pops up. The mentioned

Re: [Carbon-dev] Problem using Qpid client libraries with JMS transport

2011-02-01 Thread Lahiru Gunathilake
Hi Rajika, This is because we already have commons-codec in our OSGi environment and OSGi cannot load the same class in two Jar files, when you copy required jars in to lib/core/WEB-INF/lib you need to make sure you do not duplicate anything we already have and that is why we have used a merged

Re: [Carbon-dev] Problem using Qpid client libraries with JMS transport

2011-02-01 Thread Rajika Kumarasiri
Thanks for the pointer I'll take a look. Rajika On Wed, Feb 2, 2011 at 10:18 AM, Lahiru Gunathilake lah...@wso2.com wrote: Hi Rajika, This is because we already have commons-codec in our OSGi environment and OSGi cannot load the same class in two Jar files, when you copy required jars in