[jboss-dev-forums] [Design of JBoss jBPM] - Re: Rework of jBPM deployment within JBoss

[tom.baeyens@jboss.com]

"david.lloyd at jboss.com" wrote : "kukeltje" wrote : I agree, that he/she should have the option, but that should also be the case for changes in the .xml file. (small typo's in some text e.g.) and what about the forms....
  |   | 
  | 
  | Exactly.  That's why I said to hash the semantic graph structure, rather than the file itself.  The only change that absolutely requires a deployment of a new version is a change in the graph structure.  For any other change, it should be controllable by the user whether a new version is deployed.

i don't think it's good to have a model that has a complicated calculation on wether or not it will redeploy.

in development it doesn't matter if you redeploy too much.

in production you won't update the file that often.

so i don't really see a problem with just using a hashcode of the total process archive, preferrably in combination with the timestamp of the file.   without inspecting the contents of the deployed process

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052172#4052172

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052172