JobExecutor seems to be exposed as a property of the jbpmConfiguration. It is not one of the built-in service factories like authentication, persistence or scheduler. That said, if you were to externalize the bootstrapping of JobExecutor, you will have to get JbpmConfiguration to be knowledgable about your instance of JobExecutor. Now, JbpmConfiguration uses the object factory to locate the job executor using a string key value of "jbpm.job.executor". I haven't tried this, but if you are using the spring modules jbpm integration, they replace the default ObjectFactory with one that uses object factory keys as lookups in a spring context. Theoretically, this should mean that you can instantiate the JobExecutor in Spring and all you have to do is make sure the id value is 'jbpm.job.executor'. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4181666#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...