[ 
https://issues.apache.org/jira/browse/QPID-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547952#comment-14547952
 ] 

Rob Godfrey commented on QPID-6545:
-----------------------------------

In terms of a date for a proper fix... I'm not sure we have a definitive date 
for the next release yet.... it will definitely be included then.

This issue is a little bit of a pain because it will introduce an interop issue 
for anyone using mixed old/new versions of the client (and using unicode 
characters between 127 and 255)... also we need to decide whether we should 
make the client behave like 0-9-1 (and use UTF-8) even when operating in 0-8 or 
0-9 mode.  Moreover since the code in question is in the common library, it 
also affects the behaviour of the Java Broker.

I've been working on a patch over the weekend, but whatever we do is likely to 
lead to some interop issues and I want to discuss with a few people exactly how 
we want to handle that.

> malformed cyrillic strings that passed as TextMessage's property
> ----------------------------------------------------------------
>
>                 Key: QPID-6545
>                 URL: https://issues.apache.org/jira/browse/QPID-6545
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: 0.32
>         Environment: Windows 8 x84 Russian, RabbitMQ 3.1.5
>            Reporter: Nikita Konev
>         Attachments: Runner.java, screenRabbit.png
>
>
> When I attempt pass string that contains cyrillic symbols, it is malformed.
> I see malformed string in Rabbit's web interface and in java code which 
> receives messages from Rabbit.
> Java src in utf8 Runner.java:38 and rabbit's screen attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to