It's also fixed for Camel 2.9.3 and Camel 2.8.6.
--
View this message in context:
http://camel.465427.n5.nabble.com/DefaultUnitOfWork-doesn-t-copy-headers-from-the-original-message-if-it-s-a-JmsMessage-tp5518546p5675559.html
Sent from the Camel Development mailing list archive at Nabble.com.
Hi,
A short status update:
Regarding the expectation I had concerning the valid Java identifier check
that AMQ does ignore:
> However what I also don't get is that according to [2] the JMS
> specification states that header names must be valid Java identifiers, but
> ActiveMQ (5.5.1) seems to al
Ok, applied it only to trunk for Camel 2.10.0 because it's to late for
Camel 2.9.1
Best,
Christian
On Tue, Feb 28, 2012 at 9:02 AM, Claus Ibsen wrote:
> Hi
>
> Yeah the headers can most likely be copied today if the JMS brokers do
> not barf anymore.
>
> However I had hoped in the mean time we
Hi
Yeah the headers can most likely be copied today if the JMS brokers do
not barf anymore.
However I had hoped in the mean time we had fixed this and released
Camel 3.0, where we can optimize the logic
to only copy on demand. I once had some experimental code for this to
check the routes if the
Hi Christian,
I did verify it as well and indeed copying headers would also work even if
we deal with JmsMessage as well. However I've got no idea about the comment:
// cannot copy headers with a JmsMessage as the underlying javax.jms.Message
object goes nuts
Which came across the revision [1].
Hello!
In DefaultUnitOfWork (line 86 -93) we have the following code:
if
(exchange.getIn().getClass().getSimpleName().equals("JmsMessage")) {
this.originalInMessage = new DefaultMessage();
this.originalInMessage.setBody(exchange.getIn().getBody());
// c
