- If the config file is not named 'jbpm.cfg.xml' -> this is a bug in 3.2.3.
Rename the file to jbpm.cfg.xml and it is fixed.
- If not, having the config file on the classpath usually does the trick
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166562#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...