Hi I was wondering if you should use a different constant that = JMS.
So this one should be changed: <property name="transportType"> <util:constant static-field="com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ"/> </property> To: <property name="transportType"> <util:constant static-field="com.ibm.mq.jms.JMSC.MQJMS_CLIENT_JMS_MQ"/> </property> Notice: That the 2nd is a JMS (there is not a NON). This constant is the "1" I have sent to you in my sample, so it could probably be configured as: <property name="transportType" value="1"/> Med venlig hilsen Claus Ibsen ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: JavaRat [mailto:[EMAIL PROTECTED] Sent: 6. oktober 2008 09:52 To: [email protected] Subject: RE: Bridging the ActiveMQ with IBM Websphere using Camel You are correct here Claus, using the parameter: <property name="transportType"> <util:constant static-field="com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ"/> </property> seems to make no difference at all and we should remove it. Instead we tried using: <property name="transportType" value="1" /> This unfortunately didn't have an effect on the result. Taking a dive into servicemix-jms is the next step for sure here! This might reveal some answers. >From what I understand camel JMS is based on org.springframework.jms.core.JmsTemplate? We could perhaps make use of this? -- View this message in context: http://www.nabble.com/Bridging-the-ActiveMQ-with-IBM-Websphere-using-Camel-tp19623329s22882p19833403.html Sent from the Camel - Users mailing list archive at Nabble.com.
