I never seem to be able to connect to that damn sorceforge cvs (grrrr!), so I
may be duplicating work here. I have the alpha and don't see anything besides a
stubbed out class called "ParallelSplit.java".
After digging into the problem, it seems to me that a new class called
ForkAsync could do the trick. It would simply do this portion of the logic
differently:
// phase three: launch child tokens from the fork over the given transitions
iter = forkedTokens.iterator();
while( iter.hasNext() ) {
ForkedToken forkedToken = (ForkedToken) iter.next();
Token childToken = forkedToken.token;
String leavingTransitionName = forkedToken.leavingTransitionName;
ExecutionContext childExecutionContext = new ExecutionContext(childToken);
if (leavingTransitionName!=null) {
leave(childExecutionContext, leavingTransitionName);
} else {
leave(childExecutionContext);
}
}
The join and fork currently work together in a rather sensitive / co-operative
manner. Basically the join doesn't allow a token thru until all tokens have
reached the join. The join "rejectes" a token by returning. This causes the for
loop of the join (above) to continue processing. I am not sure what will happen
if there is no for-loop to come back to. And I am unsure of how thread safe
jBPM is... we will see...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911224#3911224
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911224
-------------------------------------------------------
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
