Support for Queue Selectors

[jlplasce]

As of now, RMQSession still throw an exception when a new consumers to queues is created with selectors:

rabbitmq-jms-client/src/main/java/com/rabbitmq/jms/client/RMQSession.java

Line 834 in d8a716f

public MessageConsumer createConsumer(Destination destination, String messageSelector) throws JMSException {

This is a definite use-case for JMS users trying to use this library to interface with RMQ

[michaelklishin]

If something hasn't been added in years there is often a reason for it: in the original protocol supported by RabbitMQ, "queue selectors" happen at a different stage that JMS assumes.

It will take a while to get to a truly protocol agnostic core and then some more time for this client to be migrated to, say, use a different protocol (potentially streams).

[acogoluegnes]

Message selection is implemented at the exchange level for JMS topics. A topic subscriber has its own AMQP queue and its optional message selector is known at creation time, so messages can be filtered out during the routing phase, not once they reached the destination, when they are about to be dispatched.

This would be a different story with queues, as the message next in line would need to be matched against the optional consumer message selector, and dispatched accordingly (to the consumer or to the next one).

This is the first time the support for message selectors in JMS queues has come up in more than 6 years of maintaining the RabbitMQ JMS client in my case.