Thanks for all the responses! @Johan Version numbers in props? I'll probably go in that direction, but having the jBPM version number in props would bring up all sorts of problems. What happens if I or the three letter company misses a deployment. What happens if someone goofs. Once the system is out of sync you would have a pretty hard time figuring out what is going on and getting back on track. But it could work. Have to go through the error szenarios.
Another idea would be to place some kind of marker in the processDefinition itself and check if that exists / matches. Worstcase would be an unconnected 'marker node' with a version number coded in a transition or something like that (yuck, maybe I'll find something better.) @Elmo Sure everything is contained in the EAR. The problems is getting it into the database. jBPM can't do very much with *.pars in a EAR :-( Still taking suggestions :-) Rainer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916843#3916843 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916843 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
