Hi,
Yes ofcourse, not specifying in userguide the meaning of concurrent to
fork node is really misleading. I would have not wasted my time. Nevertheless
lets hope jbpm will comeup with an alternative approach. As we are not using
any EJB stuff (only jsps and servlets), this behaviour of fork will be of big
headache to us.
I need some clarification to the approach specified by Ralfoeldi, please
clarify me if possible.
Lets consider a simple process definition with start-state, fork node
with two childs, a join and an end-state.
After calling/passing a message to JMS, an action to be executed is
decided based on parameters passed. ....thats fine. After that I need to signal
token to get on to next state (lets say next fork child), right! Until then
action that is associated with next fork child is not executed. Am I right.
Lets go with an eg., it seems to me to make current fork approach(which
is sequential) to parallel is something like splitting a sequential program as
follows::
| step-1
| step-2
| step-3
| ..
| step-10
|
| step-11
| step-12
| step-13
| ..
| step-20
|
|
| Above steps needs to be splitted in such a manner so that first 10 steps
and next 10 steps needs to be run parallely (concurrently)!
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911105#3911105
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911105
-------------------------------------------------------
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