camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Pimlott (JIRA)" <>
Subject [jira] [Commented] (CAMEL-9002) Headers set within velocity header are not saved when using custom VelocityContext
Date Thu, 23 Jul 2015 17:11:04 GMT


Chris Pimlott commented on CAMEL-9002:

I am using velocity templates to format email messages.  Being able to set headers is very
handy in order to generate the subject line.

#set( $headers.subject = "[$client] New project created: $projectName" )

However, I also have to put a lot of boilerplate in the template to initialize variables depending
on the domain object message body:

#set( $request = $body )
#set( $client = $request.client[0] )
#set( $requestNumber = $[0].requestNumber )
#set( $projectName =   $[0].projectName )
#set( $sourceLocale =  $[0].sourceLocale )

Have all these initializations in the template is confusing for the users and invites potential
errors.  So I was looking for a way to pre-initialize the context with my domain-specific
variables, while still waiting to be able to get values "out" of the template for subject,
from, etc.  I really don't specific care about making a new velocity context, just adding
a few new variables.

> Headers set within velocity header are not saved when using custom VelocityContext
> ----------------------------------------------------------------------------------
>                 Key: CAMEL-9002
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.15.2
>            Reporter: Chris Pimlott
>            Priority: Minor
>         Attachments:
> 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

View raw message