[jira] [Commented] (CAMEL-9002) Headers set within velocity header are not saved when using custom VelocityContext

["Chris Pimlott (JIRA)" <ji...@apache.org>]

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

Chris Pimlott commented on CAMEL-9002:
--------------------------------------

Adding a test case that demonstrates this.  {{VelocityContextHelper.generateVelocityContext}} generates a velocity Context the exact same way that {{VelocityEndpoint.onExchange}} does when none already exists, but it doesn't work since it receives a different Exchange instance than VelocityEndpoint does.

> Headers set within velocity header are not saved when using custom VelocityContext
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-9002
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9002
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.15.2
>            Reporter: Chris Pimlott
>         Attachments: VelocityContextHeaderSetHeaderTest.java
>
>
> Normally, any headers set within the velocity header are preserved as headers on the out message.  However, this does not work if you use your own VelocityContext via the CamelVelocityContext.  This is because VelocityEndpoint relies on the fact that the "headers" entry in the velocity context normally points directly to the current Exchange's in headers.  This is not likely true when using an existing velocity context.
> A more foolproof solution might be to look for and explicitly copy any updated headers from the velocity context to the out message.



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