[
https://issues.apache.org/activemq/browse/CAMEL-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Mueller updated CAMEL-2023:
-------------------------------------
Attachment: camel-velocity.patch
camel-velocity-tests.patch
> Allow the usage of velocity templates, which are placed/defined in the
> exchanges In message header or attachment
> ----------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-2023
> URL: https://issues.apache.org/activemq/browse/CAMEL-2023
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-velocity
> Environment: All
> Reporter: Christian Mueller
> Fix For: Future
>
> Attachments: camel-velocity-tests.patch, camel-velocity.patch
>
>
> It would be nice, if the camel-velocity component also read templates from
> the exchange In message header or attachment. We could define this with
> following uri's (like in the camel-mina component):
> {code}
> velocity://header:templateHeaderName respectively
> velocity:header:templateHeaderName
> {code}
> and
> {code}
> velocity://attachment:templateAttachmentName respectively
> velocity:attachment:templateAttachmentName
> {code}
> I need this flexibility in a project, because the template, which we have to
> use, must be calculated at runtime and depends on some attributes of the
> message In body like:
> - Which event has triggered this exchange?
> - Which customer will receive this message?
> - Which protocol is used (smtp, smpp, xmpp, ...)?
> I add a more technical description of my requirements in form of four unit
> tests (see camel-velocity-tests.patch). :-)
> The second attachment (camel-velocity.patch) contains the patch, which I have
> developed to fulfill my requirements. I hope with this contribution, I can
> make camel a little bit better, than this great framework is already.
> Regards,
> Christian
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
