Hi Dejan!
Thank you for explanation, now it seems clear to me.
--
View this message in context:
http://www.nabble.com/Stomp-and-content-length-tp22960715p22969783.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Sorry, I should have googled better to find the email from Dejan:
http://mail-archives.apache.org/mod_mbox/activemq-users/200810.mbox/%3c48f72a4c.4070...@ttmsolutions.com%3e
Well, as far as I understand, this is considered as not an ActiveMQ bug, but
stomp client's one? Please clarify :)
--
View
Yury Batrakov wrote:
>
> This seems reasonable, but Ruby Stomp library, I've got from gems always
> sets 'content-length', so JSON text, I send from Ruby code don't want to
> turn to Java's ObjectMessages.
>
Oh, I think I can explain while it is done
Hi all!
I'd like to ask for advice about one problem in Stomp protocol that I'd
faced. Looks like Stomp protocol have some agreement that messages without
'content-length' header are considered to be text messages and ones with
content-length is set are binary. The same logic is implemented in
tr
Hi Dejan,
Thank you for your help, it's working now. There were two points that should
have been took into account: first one is to configure XStream as you noted
below and the second one is to be careful enough and not to be misguided by
http://activemq.apache.org/stomp.html that states that "tr
Hi Dejan,
Thanks for your help! I'll try this out as soon as I have time for this and
will notify this thread about the result.
Dejan Bosanac wrote:
>
> Hi Yury,
>
> note that you have to configure XStream properly so it can use your class'
> annotations, like
>
>name="xstream">
>
Hi all!
I'm trying to force Ruby and Java code to interoperate between each other by
means of ActiveMQ's stomp. I already have a Java classes that send
ObjectMessages to each other and want these messages to be delivered and be
unmarshalled in Ruby code. I read http://activemq.apache.org/stomp.h
