[
https://issues.apache.org/activemq/browse/CAMEL-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-1689:
-------------------------------
Fix Version/s: 2.1.0
Thanks for reporting.
James Strachan had a look and came up with:
[10:00] <jstrachan> davsclaus: yeah, looks like we could let folks specify
those headers; it'll be a tad complex to implement given the complex code path
in JmsProducer - and the fact that we wanna clear down the fact that we are
customizing the QoS on the JmsTemplate after we have sent them (so we might
wanna create a new temporary JmsTemplate if any of the QoS headers are
specified on the message) - but its possible, yes
I put it on the roadmap for Camel 2.1.
But maybe we take a stab at it before so it will be in 2.0.
> JMS-Headers are ignored in Producer
> -----------------------------------
>
> Key: CAMEL-1689
> URL: https://issues.apache.org/activemq/browse/CAMEL-1689
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-jms
> Affects Versions: 2.0-M1
> Reporter: Siegfried Wirth
> Fix For: 2.1.0
>
>
> Camel jms producer ignores some JMSHeaders. For example the header
> JMSPriority is ignored - due to the comment in the code, because it is set by
> the producer. But it should not only be set by the produer due to the
> received message, it should also be possible to set a priority using the
> JMSPriority header on the consumer. (See also the option preserveMessageQos
> on the jms endpoint - if every JMSHeader is ignored by the producer it is
> impossible to set Qos-Properties on the message.)
> The reason for the bug is in
> org.apache.camel.component.jms.JmsBinding#appendJmsProperty.
> The follwoing JMS message headers are useful for sending messages and
> therefore should be copied to the jms message:
> - JMSDestination
> - JMSDeliveryMode
> - JMSExpiration
> - JMSPriority
> - JMSMessageID
> - JMSTimestamp
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
