Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of davidkarlsen@gmail.com
 designates 209.85.219.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGB5yNkn-zfmKvjzJvfukNKsgTBjE=EUdfz-c_h0eyN-E+sP=Q@mail.gmail.com>
References: <1360792007924-5727563.post@n5.nabble.com>
	<CAGB5yNnWn9P+WJgnjfr6-f+VOiAvBu2h58rzT=WMLzfeHS9V_w@mail.gmail.com>
	<1360855368660-5727605.post@n5.nabble.com>
	<CAGB5yNkn-zfmKvjzJvfukNKsgTBjE=EUdfz-c_h0eyN-E+sP=Q@mail.gmail.com>
Date: Thu, 14 Feb 2013 18:28:26 +0100
Message-ID: 
 <CAGO7Ob3PvLfNiNOrFP6XEf3ULeZP5jS15eRS+SJvNHo+H1uOpg@mail.gmail.com>
Subject: Re: Always receive String Message even with jmsMessageType set to
 Bytes
From: David Karlsen <davidkarlsen@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=e89a8fb1fbba1e538c04d5b2963d

--e89a8fb1fbba1e538c04d5b2963d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Oh- of course. I overlooked the fact that it was a consuming route. Btw.
Wmq sets a custom IBM prefixed property defining the sending charset.
Ping me directly if you want me to look it up tomorrow at work where I have
the code.
Den 14. feb. 2013 16:44 skrev "Claus Ibsen" <claus.ibsen@gmail.com>
f=F8lgende:

> On Thu, Feb 14, 2013 at 4:22 PM, yxzhao <yxzhao@stonewain.com> wrote:
> > We can verify that if the MQ message is sent with MQMessage.format =3D
> > MQConstants.MQFMT_STRING, then our route will receive text message.
> > Otherwise, it will receive a byte array. Actually, the sending app uses
> the
> > same write bytes method to put the message into the queue. The same
> message
> > can be received as bytes when using MQMessage.readFully method.
> >
> > Also, we need to know the charset that camel/jms uses to convert the
> bytes
> > into string to revert the text message back to bytes since we need to g=
et
> > the original binary values.
> >
>
> It is not Camel doing anything there. Camel uses the JMS Client to get th=
e
> data.
>
> Camel receives a javax.jms.Message which comes in different
> implementations.
> So Camel check if instanceof TextMessage, then its a text. If
> instanceof BytesMessages its a bytes message  etc.
>
> Under the hood its the JMS client, and in your case IBM WebSphere
> being the JMS client.
>
>
> > Any suggestions?
> >
> >
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/Always-receive-String-Message-even-with=
-jmsMessageType-set-to-Bytes-tp5727563p5727605.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>

--e89a8fb1fbba1e538c04d5b2963d--