Then the culprit is probably jms.jar. Andreas
On Sat, Oct 25, 2008 at 01:07, djohnjimmy <[EMAIL PROTECTED]> wrote: > > Hi Andreas, > > Thanks for the quick response. But I dont have that jar on my WAR or > classpath. > > Jars in my WAR file : > > avalon-framework-4.1.3.jar jboss-el-2.0.0.GA.jar > org.springframework.web.servlet-2.5.5.A.jar > commons-beanutils-1.7.0.jar jms.jar > oro-2.0.8.jar > commons-codec-1.3.jar > jsf-facelets-1.1.14.jar pat-1.0.jar > commons-collections-3.2.jar jsp-2.1-6.0.0.jar > providerutil-1.2.1.jar > commons-digester-1.8.jar jsp-api-2.1.jar > providerutil.jar > commons-discovery-0.2.jar jsr173-api-1.0.jar > resolver-1.0.jar > commons-el-1.0.jar jstl-1.1.2.jar > shale-core-1.0.4.jar > commonservices.jar log4j-1.2.12.jar > shale-validator-1.0.4.jar > commons-fileupload-1.0.jar logkit-1.0.1.jar > spring-2.5.5.jar > commons-lang-2.4.jar > org.springframework.aop-2.5.5.A.jar spring-webmvc-2.5.5.jar > commons-logging-1.1.jar > org.springframework.beans-2.5.5.A.jar standard-1.1.2.jar > commons-validator-1.3.1.jar > org.springframework.binding-2.0.3.RELEASE.jar stax-api-1.0.1.jar > com.springsource.org.aopalliance-1.0.0.jar > org.springframework.context-2.5.5.A.jar tomahawk-1.1.6.jar > com.springsource.org.apache.commons.logging-1.1.1.jar > org.springframework.core-2.5.5.A.jar xbean-1.0.jar > connector.jar > org.springframework.faces-2.0.3.RELEASE.jar xbean_xpath-1.0.jar > fscontext-1.2.beta3.jar > org.springframework.js-2.0.3.RELEASE.jar xmlbeans-2.3.0.jar > fscontext.jar > org.springframework.web-2.5.5.A.jar xmlbeans-qname-1.0.jar > javassist-3.8.0.GA.jar > org.springframework.webflow-2.0.3.RELEASE.jar xmlpublic-1.0.jar > > > These are the jars in my Appserver lib : > > activation-impl.jar commons-collections-3.2.jar ext > j2ee.jar nif.jar sib.api.jmsra.rar > urlprotocols.jar > aspectjrt.jar commons-digester-1.8.jar ffdcSupport.jar > jacl.jar pc-appext.jar sib.ra.rar util.jar > base.jar commons-discovery-0.2.jar htmlshell.jar > launchclient.jar physicalrep.jar sljc.jar webadmin > bootstrap.jar commons-el-1.0.jar installver.jar > lmproxy.jar pmirm4arm.jar spy.jar WMQ > bsf-engines.jar commons-lang-2.4.jar installxml.jar > mail-impl.jar rrd-appext.jar spy-sl.jar wsatlib.jar > commandlineutils.jar EJBCommandTarget.jar iscdeploy.jar > marshall.jar rsadbutils.jar sqlserver.jar > wsif-compatb.jar > commons-beanutils-1.7.0.jar el-api-1.0.jar ivblogbr.jar > myfaces-api-1.2.4.jar rsahelpers.jar startup.jar > commons-codec-1.3.jar el-impl-1.0.jar IVTClient.jar > myfaces-impl-1.2.4.jar serviceadapter.jar tcljava.jar > > > Andreas Veithen-2 wrote: >> >> Try to remove the geronimo-jms_1.1_spec-1.1.jar file from your WAR or >> EAR. That should solve the problem. >> >> Andreas >> >> On Sat, Oct 25, 2008 at 00:22, djohnjimmy <[EMAIL PROTECTED]> wrote: >>> >>> I am facing the same problem although with JSF, Spring, MQ and WAS. >>> >>> JSF requires us to use change Class loader order to "Classes loaded with >>> application class loader first" and with the configuration - the >>> queueConnectionFactories wont initialze... >>> >>> And it WAS throws the following exception : >>> >>> Caused by: java.lang.IllegalArgumentException: Cannot convert value of >>> type >>> [com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle] to required type >>> [javax.jms.ConnectionFactory] for property 'connectionFactory': no >>> matching >>> editors or conversion strategy found >>> >>> If we Change Class loader order to "Classes loaded with parent class >>> loader >>> first", then JSF will not work. >>> >>> Looks like its either JSF or MQ for us on WAS. Any ideas anyone? >>> >>> >>> >>> >>> >>> >>> callagc4 wrote: >>>> >>>> >>>> Hi, >>>> >>>> I have set up an MQQueueConnectionFactory in Websphere. I have >>>> configured >>>> my axis2.xml to use this factory for my default JMSListener. On startup >>>> the application is successfully finding the Factory reference in the >>>> websphere jndi context however i am receiving the following exception >>>> >>>> "com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle incompatible with >>>> javax.jms.ConnectionFactory" >>>> >>>> This appears to be a classpath issue on the server as i have configured >>>> the client to use the same context and jndi reference and it has no >>>> problem creating the MQQueueConnectionFactory and placing messages on >>>> the >>>> queue. The client is a standalone java client, it is running on the ibm >>>> websphere jre and i have placed the following classes on the classpath: >>>> ibm-jaxrpc-client.jar >>>> idl.jar >>>> j2ee.jar >>>> messagingClient.jar >>>> naming.jar >>>> namingclient.jar >>>> sas.jar >>>> >>>> Another point to note is that this issue depends on the classloader >>>> policy. When the ploicy is set to Application first - single loader i >>>> get >>>> this issue. However when the ploicy is set to Application first - >>>> multiple >>>> loaders the listener initializes. unfortunately our application >>>> contraints >>>> require that our policy is Application fisrt - single loader. >>>> >>>> Has anybody seen this issue before or are there any ideas as to what may >>>> be causing this incompatablility issue? >>>> >>>> Cheers, >>>> Cathal >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Axis2-JMSListener-on-Websphere-tp15165852p20158727.html >>> Sent from the Axis - Dev mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > -- > View this message in context: > http://www.nabble.com/Axis2-JMSListener-on-Websphere-tp15165852p20159210.html > Sent from the Axis - Dev mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
