Update : 

The case where the log sequence is out of order only happens if I cancel the 
task, but if I remove the task, the log is ok. 

Now after playing around for a while with canceling and removing task 
instances, I just found something that I really don't understand.

Base on the question no 2 that I've posted before. Removing the unfinished task 
instances will indeed trigger signaling on the task node causing it to move to 
state c. But if I replace the state c with another task node like this :


  |     "<process-definition>" +
  |     "  <start-state name='a'>" +
  |     "    <transition to='b' />" +
  |     "  </start-state>" +
  |     "  <state name='b'>" +
  |     "    <transition to='t' />" +
  |     "  </state>" +
  |     "  <task-node name='t' create-tasks='false'>" +
  |     "    <event type='node-enter'>" +
  |     "      <action class='test.CreateTasks' />" +
  |     "    </event>" +
  |     "    <task name='watch movie amadeus'>" +
  |     "      <event type='task-end'>" +
  |     "        <action class='test.CheckTasks' />" +
  |     "      </event>" +
  |     "    </task>" + 
  |     "    <transition to='c' />" +
  |     "  </task-node>" +
  |     "  <task-node name='c' >" +
  |     "    <task name='watch movie amadeus 2'>" +
  |     "      <assignment class='test.AssignToJack'/>" +
  |     "    </task>" + 
  |     "    <transition to='end'>" + 
  |     "  </task-node>" +
  |     "  <end-state name='end' />" +
  | 
  |     "</process-definition>"
  | 


Now, If I just execute the process definition above (all the way from start 
state to end state) using the same jbpmContext object, then everything is ok. 
But if i do this :

Execute the process from start state until the token enter task node c (where 
the task ''watch movie amadeus 2'' is assigned to Jack) using the same 
jbpmContext object.

Create a new jbpmContext and continue the process by finishing the task ''watch 
movie amadeus 2'' for jack. 

All of the sudden all the task that has been removed at task node c appear 
again here as unfinished task instances, thus the token will stay at this node 
because of it

Like I said before, this 'removed task instances appear out of nowhere on task 
node c' only happens if I create a new jbpmContext object. It won't happen if I 
keep continue the process using the same jbpmContext that I use for finishing 
task instances on task node t (where the task instances removing happens), it 
will just simply move the token to end node and finish the process which is the 
correct thing.

I really hope somebody could clarify this.....please help.


Thx and Regards,

Martin
 


View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952592#3952592

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952592

All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to