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]. My assumption is that it used to cause
problems to copy the jms headers in old days of ActiveMQ (2009) so why this
comment.
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 allow even non valid Java Identifiers as header name! I
tried with "%" which is not a valid Java Identifier:
javax.lang.model.SourceVersion.RELEASE_6.isIdentifier("%");
And the test still passed:
mockResult.expectedHeaderReceived("%", "header-value");
I hope Claus can help us regarding this question. BTW just in case you get
some spare time would you please take a look at [3] as well?
Thanks.
[1] http://svn.apache.org/viewvc?view=revision&revision=792966
[2] http://camel.apache.org/jms.html#JMS-MessageHeaderMapping
[3] http://camel.465427.n5.nabble.com/ObjectConverter-problem-td5517376.html
Babak
--
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-tp5518546p5518888.html
Sent from the Camel Development mailing list archive at Nabble.com.
