hi tom, thanks for the return, i will see if i have all acces to cvs/svn to see what you commit. ok concerning last part of the patch it's only a refactor by externalisation of context creation/closing/error handling made by old executeJob(Job) under JobExecutorThread soo it's the same thant before. (Incremetal refactoring to limit impact of modifications). to answer Fady: I just adapt Some Coding pattern "inspired" by Spring and i adapte to the current project without add dependencises with Spring soo dont worry. but now decoupling is sufisant to permit Sprint or Other kind of framework. Jbpm project is independant of integartion framework and it must continue to be. About : "And what would be left to do to include a complete integration with Spring?" it's a large domain, and there is no real answer!!! Because there is no only one complete integration with Spring or other framework but multiple coresponding to your need, your existing software, and level of integration or use of framworks. Soo the good question can be more : what would be left to do to to permit to use Jbpm under all kind of architecture ? :-) I think there is some hard coded things or some part of implementation that are no in corespondance with other in terme of design. But i prefer threat all those point later with concret and pre-package proposition. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091394#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...