What benefit does using an ejb for this purpose provide, apart from transaction management? I think making transaction handling configurable is more appropriate. The web application should be able to use the jbpm api without adding a layer of abstraction upon it. The only difference in an enterprise environment should be how jbpm manages the transaction internally. In the standalone case it would use hibernate directly (for example); in the enterprise case it would use JTA to locate/create and manage the transaction. But it should all happen behind the scenes; the jbpm txn management api should handle this transparently. I'm not sure I like the idea of redoing the web application actions in terms of the command pattern, because I wouldn't expect users to have to think in those terms; in many ways this application is a definitive jbpm example application. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003017#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...