Hi Yury, Stomp protocol (in its 1.0 version) does not define anything regarding message types, so this support for binary messages using content-type was implemented in the early implementations in ActiveMQ. We implemented support for map and object messages later using message transformations. So, since there is no mention of content-length and message types in the spec, you can't say it's a "bug" either in Ruby client nor ActiveMQ, but only that the client is not compatible with this ActiveMQ specific feature.
All this will be much better defined in Stomp 1.1, which will be hopefully implemented for ActiveMQ 6. But your client will also need to be Stomp 1.1 compatible. And for now it's not possible to turn this off, since it would break backward compatibility with existing clients that use this property. Maybe you can just "patch" your client and remove content-length header, if you don't plan to use binary messages? Cheers -- Dejan Bosanac Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Thu, Apr 9, 2009 at 9:54 AM, Yury Batrakov <batra...@gmail.com> wrote: > > 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 this message in context: > http://www.nabble.com/Stomp-and-content-length-tp22960715p22966128.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
