[
https://issues.apache.org/jira/browse/CXF-7235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851215#comment-15851215
]
ASF GitHub Bot commented on CXF-7235:
-------------------------------------
Github user cschneider commented on the issue:
https://github.com/apache/cxf/pull/231
No problem.
Please also remember to close the PR once the changes are applied unless it
auto closes.
Btw. If you have changes in your PR you do not need to create a new PR. You
can add commits and you can even use git reset to undo several commits, put
them into one commit and do a push -f. While this is bad in master it is ok on
a branch that only you work on.
Christian
> MessageSelector is not set in JMSConfiguration due to missing property in
> JMSEndpoint
> -------------------------------------------------------------------------------------
>
> Key: CXF-7235
> URL: https://issues.apache.org/jira/browse/CXF-7235
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 3.1.4
> Environment: JBoss EAP
> Reporter: Michel Meier
> Assignee: Christian Schneider
> Priority: Minor
> Fix For: 3.2.0
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
