Hi Aaron, another attempt:
Your processInstance is a data object that traverses a process as defined in the processDefinition. It can basically handle any variables you might need. What I was suggesting is that there might not be any need for a seperate HolidayRequest object. Just use the processInstance. If the required data is to large for jBPM to efficiently handle just keep a key to an external data obejct, but the 'leading entity', the one that knows about state etc. remains the processInstance. The other way around would be something like: long running contract (years) with various processes that are executed over a certain period, maybe even concurrently. Then it would make sense to let the contract keep track of the processInstances doing something to it. (The implementation might be the other way around, but that isn't the point.) In this case you would maybe want to ask: who is working on this contract? Just my 2 cents. As always there are a thousand different ways to solve things. Greetings View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920078#3920078 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920078 ------------------------------------------------------- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
