[
https://issues.apache.org/jira/browse/CAMEL-9002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Pimlott updated CAMEL-9002:
---------------------------------
Description:
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.
was:
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 would be to explicitly copy any updated headers from
the velocity context to the out message.
> 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)
