On Wed, Jun 27, 2012 at 12:06 PM, get1974 wrote:
> Thanks for your quick response. If I understand you correctly it was already
> fixed in newer version? If so I think we simple need to upgrade, which is a
> good idea anyway. Can you confirm whether this was fixed in the current
> production relea
Thanks for your quick response. If I understand you correctly it was already
fixed in newer version? If so I think we simple need to upgrade, which is a
good idea anyway. Can you confirm whether this was fixed in the current
production release?
--
View this message in context:
http://camel.465427
On Wed, Jun 27, 2012 at 11:57 AM, get1974 wrote:
> Hello Claus,
>
> I also have the case that we seem to loose the headers when forwarding to a
> retry queue using the errorhandler and useOriginalMessage. Zince we do not
> use the latest version I was wondering whether this was already fixed in de
Hello Claus,
I also have the case that we seem to loose the headers when forwarding to a
retry queue using the errorhandler and useOriginalMessage. Zince we do not
use the latest version I was wondering whether this was already fixed in de
current version (we are on 2.4) or will this be fixed in 3
This will be fixed in Camel 3.0 when we work on some internals in Camel.
On Wed, Sep 29, 2010 at 11:00 PM, Christian Mueller
wrote:
>
> Hello list,
>
> we are using camel-jms in conjunction with custom headers and the
> useOriginalMessage() definition in our error handler for our exception
> han
Hello list,
we are using camel-jms in conjunction with custom headers and the
useOriginalMessage() definition in our error handler for our exception
handling. We realized, that we loose all our headers in our dead letter
channel (using Camel 2.2.0.fuse-02-00). Our configuration looks like this
on
