[
https://issues.apache.org/jira/browse/CAMEL-9995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466866#comment-15466866
]
Claus Ibsen commented on CAMEL-9995:
------------------------------------
We may want to keep the current behavior and change the description of
includeAllJMSXProperties to what is the current behavior. As too many users are
dependent on how it works now. And different JMS brokers works differently.
> Camel-JMS: includeAllJMSXProperties parameter doesn't work
> ----------------------------------------------------------
>
> Key: CAMEL-9995
> URL: https://issues.apache.org/jira/browse/CAMEL-9995
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Minor
> Fix For: Future
>
>
> When we need to remove the JMSX* property from the JMS Message before create
> a Camel Message we can use the includeAllJMSXProperties parameter in the URI,
> but actually it doesn't work.
> This is because the filtering direction is IN and we are adding the filtering
> rules to the OUT filter.
> Also we need to take care of this parameter in the JMSBinding class too.
> https://github.com/apache/camel/blob/master/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsBinding.java#L183-L184
> The JMSX headers will be added (UserID and GroupID) without take in account
> of includeAllJMSXProperties.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
