[
https://issues.apache.org/jira/browse/CAMEL-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015335#comment-13015335
]
Joshua Watkins commented on CAMEL-3824:
---------------------------------------
Sorry, I should have posted the producer code as well. Both the producer and
the consumer don't support headers. This makes it a bit clunky if you are say
moving from JMS to Cometd and you want to maintain a header like CorrelationId.
I see the cometD ext section as headers (http://cometd.org/node/17). I am not
sure why they didn't call them headers but I am no cometD expert. Currently two
of the extensions they have are for authentication and a timestamp
(http://cometd.org/documentation/2.x/cometd-ext/timestamp). By looking other
protocols, such as http, these are specified typically as headers.
With that said, I guess I would expect Camel message headers to be transfered
to Cometd extensions along the same lines as JMS headers are passed.
> Allow cometd component to send message headers with the message
> ----------------------------------------------------------------
>
> Key: CAMEL-3824
> URL: https://issues.apache.org/jira/browse/CAMEL-3824
> Project: Camel
> Issue Type: Improvement
> Affects Versions: 2.6.0
> Reporter: Joshua Watkins
> Priority: Minor
>
> Currently the cometd component ignores message headers.
> ======
> Code snippet from CometdConsumer.java:
> Message message = new DefaultMessage();
> message.setBody(data);
> Exchange exchange = endpoint.createExchange();
> exchange.setIn(message);
> ======
> Exchange message headers should be maintained (perhaps with a flag?).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
