Add a boolean flag to SimpleMessageListenerContainer for declaring queues upon initialization [AMQP-30]

[spring-operator]

Mark Fisher opened AMQP-30 and commented

---

Affects: 1.0.0.M1

Issue Links:

• Move the declaration of queues, exchanges, and bindings into AmqpAdmin [AMQP-46] #1615 Move the declaration of queues, exchanges, and bindings into AmqpAdmin
  ("is superseded by")

1 votes, 1 watchers

[spring-operator]

Mark Pollack commented

This came up in the .NET implementation as well in a way. SimpleMessageListenerContainer in .NET is calling channel.queueDeclare(name) and not allowing for other queue creation options (durable, exclusive..) A boolean flag isn't enough, we need to accept org.springframework.amqp.core.Queue objects instead of names. Perhaps we can have a type converter perhaps of a simple string to a Queue to simplify configuration in XML.

[spring-operator]

Mark Fisher commented

once the AmqpAdmin supports declaration of all Queues, Exchanges, and Bindings within an ApplicationContext (#1615), this will not need to be addressed on the SimpleMessageListenerContainer itself. Instead, the SMLC can just have the queue "name", while the AmqpAdmin will ensure that the Queue is declared upon startup.

[spring-operator]

Lari Hotari commented

Could SimpleMessageListenerContainer directly support autodelete non-durable autogenerated queues?
It would be easier to consume messages from a topic exchange (pub-sub messaging) if you could just pass the exchangeName and routingKey to SMLC .
Is there already a nice way to listen to a topic exchange using autodelete non-durable autogenerated queues?

[spring-operator]

Lari Hotari commented

My usecase is for grails-rabbitmq plugin: http://jira.codehaus.org/browse/GRAILSPLUGINS-2494

[spring-operator]

Dave Syer commented

You can already use anonymous queues with the message listener container, as long as you configure it in Java. XML support will be added with #1670 and #1683.