[ https://issues.apache.org/activemq/browse/SM-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet updated SM-926: ------------------------------- Fix Version/s: (was: 3.2) > Add a standard JBI component for Velocity templates > --------------------------------------------------- > > Key: SM-926 > URL: https://issues.apache.org/activemq/browse/SM-926 > Project: ServiceMix > Issue Type: New Feature > Reporter: Jeff Puro > Assignee: Jeff Puro > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > I think it would be useful for ServiceMix to provide a velocity template > service engine. This would serve as an alternative to using XSLT to tranform > messages and could be particularly useful when creating the content of an > email message etc. The way it would work, in conjunction with JDOM, is that > a normalized message would be sent to the component that would inject the > properties and the content of the message into the Velocity context. You can > then use Velocity's syntax for generating XML documents or any content that > has CDATA tags around it. The properties of the normalized message would be > accessed via the $properties variable, whereas the content of the message > would be accessed via either a $content or $root variable using JDOM methods. > Since it is often nice to have Velocity templates pulled from sources other > than a .vm file (for example a database), it would be useful for the > <velocity:endpoint/> to have a pluggable resource property where the resource > could be pulled from either the filesystem, a database, etc... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.