anonymous wrote : is the ideal way of deploying .... is in the eye of the beholder So you do not call any remote services? What if you start orchestrating services? Orchestration included in your war/ear as well? Oh wait... databasescripts as well? Or do you use a hibernate param like update or something like that? Locality has long gone in our environments. As mentioned we (and I know many others) control it at a different level. anonymous wrote : Like I mentioned, the only problem with this approach is that a new process definition record is inserted into the database when each instance of our app starts up (we are distributed across donzens of hosts). This is a problem because *you* do not check it before deploying. The same code can be added to your app. anonymous wrote : that will simply do a field by field comparison of the latest version in the database and do a no-op if they're equal. Field by field? first normalized? and what about the order of elements? Again... it's not that simple. With regard to your previous question Full application is web, database, esb (jpdl also in mule) rules (in the near future). All distributed with their own deployment model, sometimes on different servers. web/business tier may always use the latest version of the processdefinition for new processes. We are still looking for a way to have multiple versions of the webapp (using all in the jbpm console is not an option) btw... dozens of hosts for one app with multiple restarst a day? What kind of company do you work for? A Telco? then again... multiple restarts.... ouch... My boss would kill me (if he could catch me) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122451#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...