activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Eirik Rønning" <larsei...@gmail.com>
Subject Re: Utf8 encoding with activemq 5.1
Date Wed, 29 Oct 2008 10:29:25 GMT
we tried this but received an error when settin the character set to utf-8The
table ACTIVEMQ_ACKS failed.

Any idea?

On Wed, Oct 29, 2008 at 11:24 AM, Dejan Bosanac <
dejan.bosanac@ttmsolutions.com> wrote:

> Can you please try and let us know
>
> Cheers
>
> --
> Dejan Bosanac
>
>
> http://www.ttmsolutions.com - get a free ActiveMQ user guide
>
> ActiveMQ in Action - http://www.manning.com/snyder/
> Scripting in Java - http://www.scriptinginjava.net
>
>
>
> � wrote:
> > I realized that by default the db used is latin. Would this help if i set
> > the db which received the values (we use jdbc persistency)
> > to utf8 instead of latin?
> >
> > On Wed, Oct 29, 2008 at 10:23 AM, Lars Eirik Rønning <
> larseirik@gmail.com>wrote:
> >
> >
> >> Well actually i would just like to take the xml which comes in and have
> >> this posted by my consumer.
> >>
> >> String myxml = request.getParameter("inputxml");
> >> sender.sendMessage(myxml);
> >>
> >> sender is a regular producer which uses the sendTextMessage method
> defined
> >> by the jms spec.
> >> Do i really need to do anything to this string if i just want to ship it
> to
> >> the que?
> >>
> >>
> >>
> >>
> >>
> >> On Wed, Oct 29, 2008 at 9:54 AM, Dejan Bosanac <
> >> dejan.bosanac@ttmsolutions.com> wrote:
> >>
> >>
> >>> Hi,
> >>>
> >>> can you post your code that creates and sends a message?
> >>>
> >>> Regards
> >>>
> >>> --
> >>> Dejan Bosanac
> >>>
> >>>
> >>> http://www.ttmsolutions.com - get a free ActiveMQ user guide
> >>>
> >>> ActiveMQ in Action - http://www.manning.com/snyder/
> >>> Scripting in Java - http://www.scriptinginjava.net
> >>>
> >>>
> >>>
> >>> � wrote:
> >>>
> >>>> Hi.
> >>>> I have a servlet which receives a post containing a utf8 encoded
> string.
> >>>> When this string is pushed to the que it seems to be stored as another
> >>>> characterset. When i use jaxb to autoprocess the xml from the que, i
> get
> >>>>
> >>> an
> >>>
> >>>> exception relating to byte offset.
> >>>> So far what i have done is used an outputstreamwriter and reencoded
> the
> >>>> string with utf8. This semmes to work.. However this is not what we
> >>>>
> >>> want.
> >>>
> >>>> When the servlet or in production the php client sends something to
> the
> >>>>
> >>> que
> >>>
> >>>> , the que is not respecting the utf8 encoding either.
> >>>> The orignal message is sendt from flex (which always uses utf8).
> >>>>
> >>>> Any easy fix for this? We would like to remoe the intermediate step
> >>>>
> >>> where we
> >>>
> >>>> now have to reencode the string.. Is this a common problem?
> >>>>
> >>>>
> >>>>
> >>>
> >>>
>
>
>
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message