Jason.Klassen at protegra.com
Wed Jun 29 15:53:31 BST 2011
Good to know, I'll omit ticket then.
From: Emile Joubert [mailto:emile at rabbitmq.com]
Sent: June-29-11 2:31 AM
To: Jason Klassen
Cc: rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] accessRequest?
Op 29/06/11 06:02, het Jason Klassen geskryf:
> I'm upgrading a project from the Rabbit 1.4 java client to 2.5.1. I
> used to do
> val ticket = channel.accessRequest( "/data" )
> and get an int back. What is the equivalent that I can do in 2.5.1?
Upgrading is a very good idea. You will probably find that the client API's have also changed a bit since 1.4 .
The "Access" class was deprecated in AMQP 0-9-1 - see http://www.rabbitmq.com/specification.html#deprecated-classes
RabbitMQ still implements access.request as a no-op for backwards-compatibility, but you should not rely on it to be present in future versions. You don't need tickets anymore, so remove the call.
VHosts play a similar role to realms. The admin guide has information on how to set them up: http://www.rabbitmq.com/admin-guide.html#access-control
More information about the rabbitmq-discuss