Hi
I think that is a very good reason for this behavior and you should
certainly try to follow the JMS specs so that camel can work well with any
JMS provider (I happen to work with ActiveMQ)
Perhaps a conclusion is that more documentation is needed. Is there a way to
contribute to documentation? I've using camel for the last couple of weeks
and gathering some practical experience I wouldn't mind to share!
Regards
Carlos Quiroz
Carlos Quiroz wrote:
>
> Hi
>
> I have been doing a system where certain messages are received in
> activemq, processed somehow (In particular I add my own custom headers)
> and then forward them to another queue.
>
> I noticed that my headers which had the format X-HEADER... were not
> forwarded and finally I found that JmsBinding has a function that filter
> headers so that only headers which form a valid Java identifier are
> forwarded:
>
> protected boolean shouldOutputHeader(org.apache.camel.Message
> camelMessage, String headerName,
>
> Object headerValue) {
> return headerValue != null &&
> !getIgnoreJmsHeaders().contains(headerName)
> && ObjectHelper.isJavaIdentifier(headerName);
> }
>
> I wonder what is the rationale for this? I can imagine some reasons but
> I'd rather ask to the list to find out
>
> Regards
> Carlos
>
--
View this message in context:
http://www.nabble.com/Some-headers-are-not-forwarded-to-JMS-destinations-tp16763376s22882p16802567.html
Sent from the Camel - Users mailing list archive at Nabble.com.
