[ 
https://issues.apache.org/jira/browse/CAMEL-7672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137536#comment-14137536
 ] 

ASF GitHub Bot commented on CAMEL-7672:
---------------------------------------

GitHub user jgquinn opened a pull request:

    https://github.com/apache/camel/pull/267

    CAMEL-7672 copy message headers that do not begin with 'camel' into STOMP 
frame headers

    CAMEL-7672 copy message headers that do not begin with 'camel' into STOMP 
frame headers

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jgquinn/camel CAMEL-7672

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/267.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #267
    
----
commit 49450c991e9cb6612d951be00cf49ec6a1cb8fa4
Author: Ryan Calder <[email protected]>
Date:   2014-09-17T16:46:02Z

    CAMEL-7672 copy message headers that do not begin with 'camel' into STOMP 
frame headers

----


> camel-stomp - Add support for reply-to header
> ---------------------------------------------
>
>                 Key: CAMEL-7672
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7672
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-stomp
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: Future
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Missing-headers-when-using-Stomp-request-reply-tp5754917.html
> This component does not support so many of the stomp headers. Also we may 
> want to map Camel headers to properties so they get propagated and send with 
> the stomp message.
> We would need to have a header mapping ala we have with the camel-jms 
> component, and a default implementation. Then people can configure a custom 
> impl for special cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to