Details
-
Improvement
-
Status: In Progress
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Much of the code around adding filters (selectors) to consumers is driven by the legacy AMQP 0-x mechanisms.
As a prelude to adding support to more filters types being defined for AMQP 1.0, the filter code should be refactored. In particular consumers in general should be able to support multiple (named) filters, which override "default" filters defined on the queue. The names associated with the filters are arbitrary. For AMQP 0-x protocols the JMS Selector filter type is supported, and a broker defined name is used.