Pete Muir of the Seam team also found this problem in the SOA branch. anonymous wrote : http://fisheye.jboss.com/browse/JBPM/jbpm.3/jpdl/jar/src/main/java/org/jb... | For Seam pageflows we don't require users to have a jbpm.cfg.xml and, with this change, jbpm blows up if jbpm.cfg.xml isn't present (afaics). The change in question was first committed to head between 3.2.2 and 3.2.3: http://fisheye.jboss.com/browse/JBPM/jbpm.3/jpdl/jar/src/main/java/org/jb... After a few emails we agreed not to throw an exception and emit a warning instead. The warning only appears if a non-default resource name is specified. if (!"jbpm.cfg.xml".equals(resource) && jbpmCfgXmlStream == null) | log.warn("jbpm configuration resource '"+resource+"' is not available"); The above change is already applied to SVN trunk. Would you care to confirm that it resolves JBPM-1376 as well? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164358#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...