xing/beetle

Beetle should be locked to amqp 0.6.x

joevandyk opened this issue · 1 comments

amqp 0.7 spits out this (when using the "rpc.rb --server" example when the server receives a message from the rpc.rb client)

DEPRECATION WARNING!

Use of mq.rb is deprecated. Instead of

  require "mq"

please use

  require "amqp"


mq.rb will be REMOVED in AMQP gem version 1.0.

Why is it deprecated? Because it was a poor name choice all along. We better not
release 1.0 with it. Both mq.rb and MQ class step away from AMQP terminology and
make 8 out of 10 engineers think it has something to do with AMQP queues (in fact,
MQ should have been called Channel all along). No other AMQP client library we know
of invents it's own terminology when it comes to AMQP entities, and amqp gem shouldn't,
too.

If you disagree with this really strongly, let us know by opening an issue at
https://github.com/ruby-amqp/amqp/issues

Thank you for understanding. AMQP gem maintainers team.

-------------------------------------------------------------------------------------
D, [2011-05-14 12:21:16#3986] DEBUG -- : Beetle: binding queue echo with internal name echo on server localhost:5672
D, [2011-05-14 12:21:16#3986] DEBUG -- : Beetle: binding queue echo with internal name echo on server localhost:5673
D, [2011-05-14 12:21:16#3986] DEBUG -- : Beetle: subscribing to queue echo with key # on server localhost:5672
D, [2011-05-14 12:21:16#3986] DEBUG -- : Beetle: subscribing to queue echo with key # on server localhost:5673
started echo server
D, [2011-05-14 12:21:20#3986] DEBUG -- : Beetle: processing message msgid:echo:591d3d00-7e5f-11e0-b68e-080027d8e375
D, [2011-05-14 12:21:20#3986] DEBUG -- : Beetle: ack! for message msgid:echo:591d3d00-7e5f-11e0-b68e-080027d8e375
E, [2011-05-14 12:21:20#3986] ERROR -- : Beetle: internal error during message processing: AMQP is not missing constant Exchange!: /home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/activesupport-2.3.11/lib/active_support/dependencies.rb:443:in `load_missing_constant'
/home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/activesupport-2.3.11/lib/active_support/dependencies.rb:106:in `const_missing'
/home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/activesupport-2.3.11/lib/active_support/dependencies.rb:124:in `send'
/home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/activesupport-2.3.11/lib/active_support/dependencies.rb:124:in `const_missing'
/home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/beetle-0.2.11/lib/beetle/subscriber.rb:121:in `create_subscription_callback'
/home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/amqp-0.7.1/lib/amqp/queue.rb:407:in `call'
/home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/amqp-0.7.1/lib/amqp/queue.rb:407:in `receive'
/home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/amqp-0.7.1/lib/amqp/channel.rb:819:in `check_content_completion'
/home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/amqp-0.7.1/lib/amqp/channel.rb:789:in `process_frame'
/home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/amqp-0.7.1/lib/amqp/basic_client.rb:10:in `process_frame'
/home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/amqp-0.7.1/lib/amqp/client.rb:107:in `receive_data'
/home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run_machine'
/home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/eventmachine-0.12.10/lib/eventmachine.rb:256:in `run'
/home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/beetle-0.2.11/lib/beetle/subscriber.rb:27:in `listen'
/home/monkey/.rvm/gems/ruby-1.8.7-p334@beetle/gems/beetle-0.2.11/lib/beetle/client.rb:197:in `listen'
rpc.rb:28

Nevermind, eric pointed out a0e5984.

Any reason why it can't be released? Otherwise, "gem install beetle" is broken.