Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (nike.apache.org: domain of gsim@redhat.com designates
 209.132.183.28 as permitted sender)
Message-ID: <4E7345A2.9000709@redhat.com>
Date: Fri, 16 Sep 2011 13:48:34 +0100
From: Gordon Sim <gsim@redhat.com>
Organization: Red Hat UK Ltd, Registered in England and Wales under Company
 Registration No. 3798903, Directors: Michael Cunningham (USA), Mark Hegarty
 (Ireland), Matt Parsons (USA), Charlie Peters (USA)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b1
 Thunderbird/3.0.10
MIME-Version: 1.0
To: users@qpid.apache.org
Subject: Re: JMS client skips string message properties
References: 
 <CAECqq8qC+3YdjS3euX+9mVwEpuf5QRWyx3mXE7wZpPr_sbgZTA@mail.gmail.com>
	<4E72452A.50709@blueyonder.co.uk>
	<CAECqq8q47w39PXKi+N_Sxr2ztinhx19+XGWCtKvmhpOCaUgNRQ@mail.gmail.com>
	<4E7308E3.7080804@blueyonder.co.uk>
 <CAECqq8paCiu6E8-zv4Qxsb05XzEYZQDMsO=0O=HVHSyufO1_sw@mail.gmail.com>
In-Reply-To: 
 <CAECqq8paCiu6E8-zv4Qxsb05XzEYZQDMsO=0O=HVHSyufO1_sw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 09/16/2011 09:42 AM, Jiri Krutil wrote:
> Hi Fraser
>
> When I call Message.toString(), I see a list of all non-string properties,
> but there is no trace of the string properties I have set in C++.
> I think the difference in behaviour that we see could be explained by
> different versions of the C++ client or broker or Java client.
>
> I was experimenting with Variant.setEncoding() on the sending side, as
> Gordon suggested, but to no avail. Unfortunatelly there is no documentation
> for this function, so it's hard to guess what the supported encodings are.
> (I was trying encodings "str8" and "UTF-8", but this did not help. My string
> only contains plain 7-bit ASCII characters.)

Yes, sorry about that, it does need addressed. The encoding you want is 
utf8 (also recognised are utf16, binary and iso-8859-15).

> By the way if the property value cannot be treated as a String in Java, I
> still don't see why is it not at least made available as a byte array.
>
> Let's wait and see if Gordon has something to say on this...

Could you get a broker trace for a simple send and receive of such a 
message? That might shed a clue at least as to which side the issue is on.

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org