camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marat Bedretdinov (JIRA)" <>
Subject [jira] Commented: (CAMEL-1543) Apply removeHeader also to the underying JMS message delegate
Date Sun, 19 Apr 2009 20:34:31 GMT


Marat Bedretdinov commented on CAMEL-1543:

Good point.

If I recall correctly as a work around you could instruct the runtime to always create a new
javax.jms.Message between from and to steps (alwaysCopyMessage=true), though this is not very
efficient when used between the same JMS broker providers on from() and to() sides.

> Apply removeHeader also to the underying JMS message delegate
> -------------------------------------------------------------
>                 Key: CAMEL-1543
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-jms
>    Affects Versions: 2.0-M1
>            Reporter: Frank Schwarz
> In case of a JMS message, header information is redundantly stored in org.apache.camel.component.jms.JmsMessage
(here Camel-Message) and in its javax.jms.Message jmsMessage delegate (here JMS-Message).
Currently you cannot remove effectively any header from the Camel-Message instance as in the
next processing step those removed headers resurrect from the underlying JMS-Message.
> Please provide any means to remove or or at least mask out those headers from the underlying

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message