Article:		Creating Email Templates with XML
Subject:		Velocity!
Date:		2003-07-15 09:15:28
From:		anonymous2
Take a look at Velocity from Jakarta. We presently use it for creating email templates. It is both easier to use and more powerful than the solution described here.

Showing messages 1 through 5 of 5.

• Velocity!
  2003-07-16 16:20:58  anonymous2 [View]
  
  
  Yes, I agree. Apart from Velocity one can also consider using XSL stylesheet which fits nicely with XML format. I am fed up seeing these custom template classes again and again! We have come a long way in standardizing the templating problem to either XSLT transformation or Velocity.
• Velocity!
  2003-07-17 16:14:32  rafeco [View]
  
  
  This approach is for plain text email. The nice thing about it is that it would be fairly easy to write an XSL transformation that would turn it into an HTML email to go along with it.
• Velocity!
  2003-07-17 03:31:21  anonymous2 [View]
  
  
  I had created a Mailing component using the XML -> MessageFormat architecture around 1.5 years back. Due to the limitation of those 9 message replacements, the classes who will create theese message holders were very complicated. Now I revamped the whole stuff to use Velocity and it is the excellent !!!! When it comes to dynamically merging the mail template and the data (e.g. Registartion confirmation to take easiest use-case) I found the Velocity based solution as best.
• Velocity!
  2003-07-17 03:30:32  anonymous2 [View]
  
  
  I had created a Mailing component using the XML -> MessageFormat architecture around 1.5 years back. Due to the limitation of those 9 message replacements, the classes who will create theese message holders were very complicated. Now I revamped the whole stuff to use Velocity and it is the excellent !!!! When it comes to dynamically merging the mail template and the data (e.g. Registartion confirmation to take easiest use-case) I found the Velocity based solution as best.
• Velocity!
  2003-07-17 03:29:58  anonymous2 [View]
  
  
  I had created a Mailing component using the XML -> MessageFormat architecture around 1.5 years back. Due to the limitation of those 9 message replacements, the classes who will create theese message holders were very complicated. Now I revamped the whole stuff to use Velocity and it is the excellent !!!! When it comes to dynamically merging the mail template and the data (e.g. Registartion confirmation to take easiest use-case) I found the Velocity based solution as best.