[CXF-7235] MessageSelector is not set in JMSConfiguration due to missing property in JMSEndpoint

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.1.4
• Fix Version/s: 3.2.0
• Component/s: Transports

Environment

JBoss EAP

• Estimated Complexity: Moderate
• Assignee: Christian Schneider
• Reporter: Michel Meier
• Created: 29/Jan/17 11:56
• Updated: 28/Nov/17 10:41
• Resolved: 02/Feb/17 17:08

Description

Hi,
i was facing the issue, that the messageSelector property for JMSConsumers in the org.apache.cxf.transport.jms.util.PollingMessageListenerContainer was not set. After digging in the source it figured out, that the attribute messageSelector is missing in the class
org.apache.cxf.transport.jms.uri.JMSEndpoint
which is used to map all JMS related properties via
org.apache.cxf.transport.jms.JMSConfigFactory to the property holding class
org.apache.cxf.transport.jms.uri.JMSConfiguration
which is used at the end to register the JMS Consumers

The Solution is to add the propertygessageSelector to class
org.apache.cxf.transport.jms.uri.JMSEndpoint
and add the mapping in org.apache.cxf.transport.jms.JMSConfigFactory

Issue Links

• links to: GitHub Pull Request #229
• links to: GitHub Pull Request #231