[
https://issues.apache.org/jira/browse/CAMEL-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118987#comment-13118987
]
Joshua Watkins commented on CAMEL-3824:
---------------------------------------
The use case for me is that our program routes messages from JMS to cometd. Due
to this we copy across some of the (although renamed) JMS headers (eg.
Messageid, JMSType, CorrelationId) into cometd headers for our clients to use
without having to alter the message body inflight.
The second bit that this patch does is add the cometd clientid and cometd
"headers" to the incoming message headers. This allows for cleaning up of
resources created for a particular client upon disconnection and validating a
user is authenticated further down the message chain.
However we can just continue to use a branched version of the component until
2.9
> 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
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: cometd_header_support_patch.txt,
> cometd_headers_support_noDotpatch.txt
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
