Since 3.1.2 (and correct in 3.1.3) the processdefinition is stored in the database as plain xml as well. Generating (and comparing) a hash for both the latest pd in the DB and the pd that is provided is fairly simple. It's none intrusive, backwards compatible etc..etc.. Normalization should take place to prevent reformatting leading to a new deployment. Maybe even a "reordering" kind of normalization since switching two nodes in jbpm does not lead to a different executional process. So start task first, then all generic nodes, task nodes etc..etc..etc... Or a reordering based on node name is another option (but what about the elements/attributs IN nodes.. hmmm... comments? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998567#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...