Hello to all,
How do we best handle multiple sub-processes? For example, a recruitment
process starts with the submission of a job order or a request. At the state
when it is ready (i.e. approved) for accepting candidates, I would want to
create a sub-process each for managing each candidate (from interview-accept or
fail, etc). The job order can proceed when it has been fulfilled (right number
of candidates accepted) or it can be forced to close and signal all pending sub
processes to abort themselves firing the necessary events.
Since the most logical approach is to do this programatically and
triggered by a user, do we still need to declare this as a subprocess in the
definition or should it be designed as a fork instead or as task-nodes? Is
there a way to control from the process definition that the candidate-process
can only be created or started if I am on the approved state?
I have a few ideas on how to do this, but I would really appreciate it if
somebody could share some of their design expertise on how best to do this. I
would be happy to discuss this. Thanks a lot.
Regards,
Elmo
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3914108#3914108
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3914108
-------------------------------------------------------
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
