Hi Rainer I've taken a completely different approach. I use the gpd to edit my process definitions from within eclipse, and then I have an eclipse launch configuration that can load any process definition straight into the database given a parameter (the process definition's name). The class invoked by the launch config can be made to point to different databases. The gpd is interactive, so why not make the loading of the process definition interactive also. Or you could also invoke the same class from an ant build to load the process definition into some database.
My ear(s) then only contain the code that interact with the process definition. For example, token.signal(), etc. - no code for loading a fresh process definition. So, when I use the application in the ear, it just uses the latest version of the process definition. Obviously I could use a specific (property driven) version of the process definition if it is a production environment. Because of the versioning jBPM does, I think it is safe to load the process definition straight into the production database - once I've tested it in my test environment of course. Hope this helps Johan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916828#3916828 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916828 ------------------------------------------------------- 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
