Look at the resource patterns (on www.workflowpatterns.com . anonymous wrote : Initially a work item comes into existence in the created state. This indicates that | the preconditions required for its enablement have been satisfied and it is capable of | being executed. At this point however, the work item has not be allocated to a | resource for execution and there are a number of possible paths through these states for individual work items. It is not always possible to know the right actor from the beginning (even not the right pool). Or it could be so computing-intensive that you let another thread or process handle the assignments async-like. This process could even "listen" for the created event, and queue it for pooling/assignment. "created" should mean: the basic stuff is there, if you want to intervene, go ahead. Maybe it should have another wording in the case of jBpm, like "ready", but then we lack the "created" event, and some implementations will really need it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921388#3921388 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3921388 ------------------------------------------------------- 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
