I agree with Heiko here. Working around JSF to generate an email ... it just feels wrong. It's not because the Seam guys are doing it, that jBPM must follow. Seam works in webapp-only environment. It makes (a bit) sense there. But what if one wants to use emailing in a Swing-jBPM app? Then they have to set up a seperate app server for the email-generating webapp? This just will not happen IRL. I also think that using Velocity would be better. Velocity is nothing more than a fast engine that fills up a template with what is provided as input. It might be not as 'fancy' as JSF, but it gets the job done in a very simple and understandable way.Users can provide their own velocity templates that can easily plugged in a jbpm process definition. Heck, you can even create a custom JPDL node for this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4209794#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...