I cannot imagine it is a problem with gravel or jbpm4jsf (and no I'm not going to try now ;-)) More likely 2 versions (might even be the same ones, but with classeds without) of jsf, which is (could be) only the case if you run it in the console. Look if the jbpm.war/ear contains jsf and if the appserver does to. If the latter is the case AND hibernate is in the appserver, not the ear/war than I'm pretty sure if you remove the jsf jar from the ear/war it will work!!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091472#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...