Hello Chad,
It appears that an attempt to establish a JMS connection with Weblogic 8.1 is the source of the problem. The interfaces returned by the javax.naming.InitialContext do not seem to match javax.jms.* interfaces (QueueConnectionFactory, QueueConnection, etc.) in the Weblogic 8.1 implementation. There are two files in axis2 libs, geronimo-spec-jms-1.1-rc4.jar and axis2-kernel-1.2.jar, that deal with JMS and I presume that the version of the JMS that they are using differs from Weblogic 8.1. Could you suggest an approach to ensure that during the run time all of the JMS will be resolved correctly (putting Weblogic jars into the aar file won't fix it since geronimo-spec-jms-1.1-rc4.jar and axis2-kernel-1.2.jar will be loaded first and loading Weblogic jars before these two will cause the problem I mentioned already). Please advice. Thanks, Swavek From: Chad DeBauch [mailto:[EMAIL PROTECTED] Sent: Monday, June 25, 2007 7:42 PM To: axis-user@ws.apache.org Subject: Re: Classpath Problem You should keep the third party jars with the aar file and tackle the problem from that angle. The jars in the WEB-INF/lib directory will be loaded first so you may have conflicts with the jars that you have in your aar or in the jars that Tomcat loads. That is why you may be getting the class not found exception. Chad On 6/25/07, Swavek Skret <[EMAIL PROTECTED]> wrote: When deploying the axis2.war I get the following error in the Tomcat log: 2007-06-25 12:19:36,018 ERROR org.apache.axis2.transport.http.AxisServlet - java.lang.LinkageError: loader constraint violation: loader (instance of org/apache/axis2/deployment/DeploymentClassLoader) previously initiated loading for a different type with name "javax/jms/QueueConnection" It is possibly related to the classpath changes I did in my Tomcat settings. When creating the aar file, I added the lib directory that included my 3rd party jar. However, I got a class not found exceptions so I changed Tomcat shared.loader classpath and added my 3rd party jars to it but now I am getting the above error. Does anyone have any idea of how to fix it? Thanks, Swavek --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
