I am very much in favor of what you call "Persistent Process Resource", which basically means just storing execution state and history in the DB. Anything else, and most importantly, all class resources should be retrieved through the classloader. This already answers your question regarding the clustering: Leave it to the deployment/classloading framework of the AS. But in general we should aim at the plain non clustered AS integration first and then worry about clustering when we need it. But you easily relay questions like this if you leverage the AS infrastructure too a large degree. I do actually have uncommitted AS integration code on my disk, that installs the process engine as a service and adds the corresponding deployers so tat you can drop *.par archives intio the deploy folder. Quiet similiar to what Bernd described in his Blog, just for AS 5. I would say, to begin with we should aim at 1) Persistent Process Resource as execution mode inside the AS 2) Add a service and deployer 3) Fix the classloading (classloader registry, reassociation upon reboot) 4) Deal with diferent versioning strategies upn deployment and server boot. We need to get this sorted before diving into clustering topics. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210594#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...