No mechanism to specify messageSelector for JMS Listener
Proxy Services Management and Transports
JMSListener goes through JMSConnectionFactory. As part of startListeningOnDestination method, it creates a consumer via JMSUtils.createConsumer. This in turn instantiates the QueueReceiver or TopicSubscriber, but in neither case are messageSelectors routed through for filtering.
I understand that the JMS transports are being improved, and I'm curious if the ability to define messageSelectors within a proxy will be put into place.
-Lucas
- Login or register to post comments
- Printer friendly version
- 157 reads











Lucas Yes, this is on my
Lucas
Yes, this is on my TODO list.. but you could raise a JIRA to make this a concrete real-user backed requirement :D
asankha