Return-Path: 
 <camel-user-return-3448-apmail-activemq-camel-user-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org
Received: (qmail 10005 invoked from network); 24 Sep 2008 11:26:39 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 24 Sep 2008 11:26:39 -0000
Received: (qmail 67749 invoked by uid 500); 24 Sep 2008 11:26:36 -0000
Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org
Received: (qmail 67724 invoked by uid 500); 24 Sep 2008 11:26:36 -0000
Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:camel-user-help@activemq.apache.org>
List-Unsubscribe: <mailto:camel-user-unsubscribe@activemq.apache.org>
List-Post: <mailto:camel-user@activemq.apache.org>
List-Id: <camel-user.activemq.apache.org>
Reply-To: camel-user@activemq.apache.org
Delivered-To: mailing list camel-user@activemq.apache.org
Received: (qmail 67713 invoked by uid 99); 24 Sep 2008 11:26:36 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Sep 2008 04:26:36 -0700
X-ASF-Spam-Status: No, hits=2.6 required=10.0
	tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Sep 2008 11:25:37 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1KiSVV-0001mb-Dm
	for camel-user@activemq.apache.org; Wed, 24 Sep 2008 04:26:09 -0700
Message-ID: <19646763.post@talk.nabble.com>
Date: Wed, 24 Sep 2008 04:26:09 -0700 (PDT)
From: JavaRat <fredrik.sassenberg@mindwell.se>
To: camel-user@activemq.apache.org
Subject: RE: Bridging the ActiveMQ with IBM Websphere using Camel
In-Reply-To: <4C1FB9C00D24A140906239533638C4D2057163D0@EXVS04.exserver.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Nabble-From: fredrik.sassenberg@mindwell.se
References: <19623329.post@talk.nabble.com>
 <4C1FB9C00D24A140906239533638C4D2057161F9@EXVS04.exserver.dk>
 <19623857.post@talk.nabble.com>
 <4C1FB9C00D24A140906239533638C4D20571620E@EXVS04.exserver.dk>
 <19643280.post@talk.nabble.com>
 <4C1FB9C00D24A140906239533638C4D2057163D0@EXVS04.exserver.dk>
X-Virus-Checked: Checked by ClamAV on apache.org


Hi Claus, many thanks for your ideas and suggestions so far!

We have tested the above tips you had. Both on their own and together
without any effect we can see on the message which ends up on our final
queue destination. Browsing the message we get on the IBM MQ queue we get
the following:


XQH .... CAMELoutputchannel
                                  queue.out

            CT ....................=C3=BF=C3=BF=C3=BF=C3=BF....
....R...MQHRF2 .............AMQ Qmgr
            <<exH ...$.....................
......................

                                        Qmgr

                      CAMELusertester...'
Vu%%._IneiZ..................
                               .........WebS
phere MQ Client for Java20080924=20
11025671    RFH .........................
MQSTR   ........,...........,<mcd><Msd>
jms_text</Msd><Type></Type></mcd>
...X<jms><Dst>queue:///queue.out</Dst>
<Tms>1222311223456</Tms><Cid></Cid>
<Dlv>2</Dlv></jms> ......
<usr><jms_IBM_MsgType dt=3D'i4'>1</jms_IBM_MsgType>
<jms_IBM_Format>MQSTR</jms_IBM_Format>
</usr>
my chocolatechip cookie recipie


Without getting into MQ details it looks very much as we have a JMSMessage
around the TextMessage which we are intending to put onto the queue. (Clues
too why we think so is we see a MQHRF2 and a RFH part.) Also we see the
MQSTR and <Msd>jms_text</Msd> beeing recognized.
=20
Our current guess (and let us assume this is the case) is that we are not
"peeling" off the camelWrapper Message before putting it onto the IBM MQ
queue.=20
How can we avoid sending our textMessage inside this camelWrapperMessage?

Have we made a misstake thinking we can use the following configuration
inside the camel-context.xml?
We refer to this bean when we use the
from(activemq:queue.in).to(ibmmq:queue///queue.out)

<bean id=3D"ibmmq" class=3D"org.apache.camel.component.jms.JmsComponent">
<property name=3D"connectionFactory">
<bean class=3D"com.ibm.mq.jms.MQQueueConnectionFactory">
<property name=3D"transportType">
<util:constant static-field=3D"com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ"/=
>=20
</property>
<property name=3D"queueManager" value=3D"MW01"/>
<property name=3D"hostName" value=3D"172.23.1.19"/>    =20
<property name=3D"port" value=3D"1414"/>
</bean>
=09=09</property>=20
=09</bean>
--=20
View this message in context: http://www.nabble.com/Bridging-the-ActiveMQ-w=
ith-IBM-Websphere-using-Camel-tp19623329s22882p19646763.html
Sent from the Camel - Users mailing list archive at Nabble.com.