Hi Slavikos,
If I am not mistaken, I think this might give you unexpected results
regarding the state of the workflow. There is only one path of execution in
this case, the root token. Once the first iteration finishes, the current node
is already the join node (end_of_user_iteration), thus the next iteration in
the for each might not transition properly. I might be wrong, so need to check
this out.
I don't know if I got what you are trying to achieve, but the way I was
doing was quite different. I had several process running concurrently, and I
created child tokens for each. I made a fork and each child process was created
on the fly, and root token continued execution only when all processes met at
the join. There were several child tokens so my root token reflected the
correct state.
But anyway, if it worked for you, then that's fine.
Regards,
Elmo
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923201#3923201
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3923201
-------------------------------------------------------
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
