You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. I wrote a java client that communicate Chat sample with openwire protocol.
2. I also rewrote StompChat sample to use latest version of as3-stomp_05,
because of unicode problem.
3. Java client sends TextMessage and StompChat receives it well.
4. Openwire client receives BytesMessage type from as3-stomp clients.
What is the expected output? What do you see instead?
Openwire clients prefer TextMessage type when String type messages.
What version of the product are you using? On what operating system?
Version: as3-stomp_05_source.zip
On Windws-XP and ActiveMQ.
Please provide any additional information below.
ActiveMQ converts message to BytesMessage for openwire client, if
'content-length' header exists.
Attached changes works well for me.
Best regards,
Maeda.Masahiro at fujixerox.co.jp
Original issue reported on code.google.com by maeda.ma...@fujixerox.co.jp on 16 Apr 2008 at 2:25
Thanks Maeda. In the current version of the Stomp client there is method called
sendTextMessage that should address this issue.
See line 195:
http://code.google.com/p/as3-stomp/source/browse/trunk/org/codehaus/stomp/Stomp.
as
This method expects a String and it does not add a content-length header. I've
tested this with a couple clients that take TextMessages and it appears to work
with
them.
Original comment by dwischu...@gmail.com on 10 May 2008 at 11:39
Original issue reported on code.google.com by
maeda.ma...@fujixerox.co.jp
on 16 Apr 2008 at 2:25Attachments:
The text was updated successfully, but these errors were encountered: