You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Stan Lewis (JIRA)" <ji...@apache.org> on 2009/09/11 18:31:12 UTC

[jira] Updated: (CAMEL-1850) Velocity Component: Ability to specify velcoity resource/template as message header

     [ https://issues.apache.org/activemq/browse/CAMEL-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stan Lewis updated CAMEL-1850:
------------------------------

    Attachment: patch.txt

I looked into implementing this in camel-spring's ResourceBasedEndpoint but it felt like the solution was starting to get really complicated as that endpoint is designed to only manage one resource.  This way is definitely a lot simpler and I think is a good approach to implementing this feature.

> Velocity Component: Ability to specify velcoity resource/template as message header
> -----------------------------------------------------------------------------------
>
>                 Key: CAMEL-1850
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1850
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-spring
>            Reporter: slad
>            Assignee: Stan Lewis
>             Fix For: 2.1.0
>
>         Attachments: patch.txt
>
>
> It would be nice to have a message header that can be used to specify which velocity template to be used for the message. This allows to dynamically use different templates while still preserving velocity endpoint cache. In real life you will have more than 1 template and you use of template will change from message to message.
> Something like -
> 	
> from("direct:start")
> .setHeader("velocityTemplate", "orderDisplay.vm"); 
> .to("velocity:dummyTemplate.vm") 
> Currently to achieve this you have to define custom bean or some processor.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.