Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <334068413.1253223012248.JavaMail.jira@brutus>
Date: Thu, 17 Sep 2009 14:30:12 -0700 (PDT)
From: "Christian Mueller (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-2023) Allow the usage of velocity
 templates, which are placed/defined in the exchanges In message header or
 attachment
In-Reply-To: <104414124.1253222292201.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/CAMEL-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54324#action_54324 ] 

Christian Mueller commented on CAMEL-2023:
------------------------------------------

If you agree with this contribution, I would also update the camel-velocity component site to describe the new features (if anybody can tell me the svn url of this componets site)... :-)

Regards,
Christian

> 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.