Stomp usage fails on trunk

zacsek / activemessaging

Automatically exported from code.google.com/p/activemessaging

0 stars 0 forks source link

What steps will reproduce the problem?
1. Define a broker using stomp and clientId
2. Start ActiveMessaging
3.

What is the expected output? What do you see instead?
Expected Normal startup

Got

activemessaging/lib/activemessaging/adapters/stomp.rb:26:in `initialize':
wrong # of arguments(7 for 6) (ArgumentError)

What version of the product are you using? On what operating system?
activemessaging trunk
stomp 1.0.5

Please provide any additional information below.

Stomp::Connection#initialize signature for stomp-1.0.5 is

def initialize(login, passcode, host='localhost', port=61613,
reliable=false, reconnectDelay=5)

Are you using a modified/newer version of stomp?

Original issue reported on code.google.com by don...@gmail.com on 23 Oct 2008 at 10:58

stomp-1.0.5 does not support usage of clientId at all. The trunk of the codehaus stomp implementation does and the gem version does also. Unfortunately, the two approaches are not compatible. ActiveMessaging 0.6.1 has implemented support for the codehaus-trunk. See attached patch for support for clientId using the gem version.

zacsek / activemessaging

Stomp usage fails on trunk #39