On 06/13/2014 02:46 PM, Andrew Stitcher wrote:
On Fri, 2014-06-13 at 12:25 +, Jan Bares wrote:
Thank you Gordon, I explicitly set the encoding on property variant in
qpid-send.cpp and it worked for me too.
Do you think this might be handled better in the JMS client too. I don't
think tha
On Fri, 2014-06-13 at 12:25 +, Jan Bares wrote:
> Thank you Gordon, I explicitly set the encoding on property variant in
> qpid-send.cpp and it worked for me too.
Do you think this might be handled better in the JMS client too. I don't
think that JMS specifies what to do in this case so just
Thank you Gordon, I explicitly set the encoding on property variant in
qpid-send.cpp and it worked for me too.
Kind regards, Jan
> -Original Message-
> From: Gordon Sim [mailto:g...@redhat.com]
> Sent: Friday, June 13, 2014 1:54 PM
> To: users@qpid.apache.org
> Subject: Re: qpid-send and
On 06/13/2014 11:13 AM, Gordon Sim wrote:
I'll check in a fix for that shortly
(https://issues.apache.org/jira/browse/QPID-5814).
Done: http://svn.apache.org/r1602390
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.or
On 06/12/2014 03:06 PM, Jan Bares wrote:
Hi,
property passed with message like that:
qpid-send -b ${BROKER} -a exchange/cal --durable yes --content-string "content"
--property MyProp=MyValue
will throw MessageFormatException in getStringProperty() in Java JMS client.
The class of value is ar
