Followup on this: after much poking around to get a simplified repro, we
isolated a bug in Service Bus. Proton seems to be behaving sanely under the
circumstances.
-Original Message-
From: Rafael Schloming [mailto:r...@alum.mit.edu]
Sent: Saturday, December 20, 2014 11:20 AM
To: users@q
A second release candidate is now available here:
http://people.apache.org/~tross/qpid-dispatch-0.3rc2/
The following issues have been resolved since RC1. DISPATCH-92 was
considered a blocker since fixing it later would constitute an
incompatible change to the configuration format on a featu
Thank you for explaining this difference.
-
Best Regards,
Hamid.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/QPid-0-28-amqp1-0-Java-vs-C-client-tp7618131p7618150.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
On 01/08/2015 02:56 PM, Hamid.Shahid wrote:
Thanks Gordon,
But is it better to use /message.setContent(msgString)/ or to use
/message.setContentObject(msgString)/?
Use Message::setContentObject(). If you use setContent() the data will
be sent as a sequence of bytes rather than a utf8 string.
Thanks Gordon,
But is it better to use /message.setContent(msgString)/ or to use
/message.setContentObject(msgString)/?
-
Best Regards,
Hamid.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/QPid-0-28-amqp1-0-Java-vs-C-client-tp7618131p7618141.html
Sent from the Apache Q
On 01/08/2015 12:58 PM, Hamid.Shahid wrote:
Hi,
I have the following java jms code which sends a string message with with
some properties to a broker and this works fine.
/TextMessage message = session.createTextMessage(msgString);
String correlationId = "abc1";
message.setJMSCorrelationID(corr
Hi,
I have the following java jms code which sends a string message with with
some properties to a broker and this works fine.
/TextMessage message = session.createTextMessage(msgString);
String correlationId = "abc1";
message.setJMSCorrelationID(correlationId);
message.setObjectProperty("Message
