Neat, I overlooked the end-tasks attribute. I just applied your suggestion and the tests pass. However, if you see the log, you will notice there is a problem in the timeout scenario. Ending the tasks (by virtue of end-tasks="true") results in the token taking the default transition. After that, the timer pushes the token through the timeout transition. In total, the task node is left three times :-(
I attached the updated project to the wiki page. I like the way the process definition looks now, but the behavior is incorrect. When the node is left as a result of the user ending a task, jBPM does not signal again as the remaining tasks are ended. When the node is left as a result of a timeout, jBPM signals each time it ends one of the remaining tasks. We'd really appreciate your help to determine the cause of this anomalous behavior and how to fix it. Also, please explain how you modified the JSF bean not to show the timeout transition in your other post. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3925730#3925730 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3925730 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
