in org.jbpm.taskmgmt.exe.TaskMgmtInstance the following code is present.
public SwimlaneInstance getInitializedSwimlaneInstance(ExecutionContext
executionContext, Swimlane swimlane) {
| // initialize the swimlane
| if (swimlaneInstances==null) swimlaneInstances = new HashMap();
| SwimlaneInstance swimlaneInstance = (SwimlaneInstance)
swimlaneInstances.get(swimlane.getName());
| if (swimlaneInstance==null) {
| swimlaneInstance = new SwimlaneInstance(swimlane);
| addSwimlaneInstance(swimlaneInstance);
| // assign the swimlaneInstance
| invokeAssignmentHandler(swimlane.getAssignmentDelegation(),
swimlaneInstance, executionContext);
| }
|
So this means that if there is an initialized swimlane for a taskinstance, the
assignmenthandler will not be called again. This wil not happen if you put the
assignmenthandler directly on the task, not via a swimlane. Not sure if this is
realy a bug, as designed or just an overlooked issue.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3925892#3925892
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3925892
-------------------------------------------------------
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
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
