Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Openwire compatibility #6

Closed
GoogleCodeExporter opened this issue Mar 17, 2016 · 2 comments
Closed

Openwire compatibility #6

GoogleCodeExporter opened this issue Mar 17, 2016 · 2 comments

Comments

@GoogleCodeExporter
Copy link

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

Attachments:

@GoogleCodeExporter
Copy link
Author

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

  • Changed state: Invalid

@GoogleCodeExporter
Copy link
Author

This method works well for me.

Thanks a lot.

Original comment by maeda.ma...@fujixerox.co.jp on 14 May 2008 at 8:48

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant