I would also appriciate a single wiki site where all the requirements are collected. I want to add some comments to various points: - process versioning: What I like in the current deployment model is the control you have, YOU decide when you deploy and if you include the classes or not. And that should not be somehow automated, at least in production. - a version attribute in the xml and maybe a attribute if to include classes would be interessting option (much better than hash I think). Waiting for jbpm 3.3 should not be a showstopper for this. - normally there are many different versions with running processes around. It is quite normal in long running business processes (like Britt said) - I like the protability of jBPM very much. And I think it is a important advantage that should be kept. Today it runs in standalone, Tomcat, JBoss or other AS environments. Very important in my eyes. So some proprietary JBoss deployment should be always (or at least in the near future) additional. Thats what the people like about jBPM, it is not tied to some AS. Bernd. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053225#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...