You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/05/26 06:59:04 UTC
[jira] [Commented] (CXF-7235) MessageSelector is not set in
JMSConfiguration due to missing property in JMSEndpoint
[ https://issues.apache.org/jira/browse/CXF-7235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025903#comment-16025903 ]
ASF GitHub Bot commented on CXF-7235:
-------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/cxf/pull/231
> 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)