camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Mueller (JIRA)" <>
Subject [jira] Commented: (CAMEL-2023) Allow the usage of velocity templates, which are placed/defined in the exchanges In message header or attachment
Date Fri, 18 Sep 2009 12:10:53 GMT


Christian Mueller commented on CAMEL-2023:

Hello Claus!

Thank you for your quick reply. I think my explanation was too short...

In my project, the templates are stored in a database (because our customers have the possibility
to change the templates with a custom build application at runtime) and we don't want to have
to redeploy our service, whenever a template is modified. For this reason, we call a service
which resolves the template to use, read the template from the database and adds it to the
exchange in-message header. That's the reason, we need the functionality to read the "real"
template (not the path to the template) from the exchange in-message header (or attachment).


> Allow the usage of velocity templates, which are placed/defined in the exchanges In message
header or attachment
> ----------------------------------------------------------------------------------------------------------------
>                 Key: CAMEL-2023
>                 URL:
>             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
> {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.

View raw message