This content has been marked as final.
Show 3 replies
-
1. Re: Why should I create task in Task-node ?
kukeltje Jul 15, 2007 11:17 AM (in response to lyo)you can't create tasks in states... that is why you have to do it in a task-node
-
2. Re: Why should I create task in Task-node ?
lyo Jul 15, 2007 12:32 PM (in response to lyo)"kukeltje" wrote:
you can't create tasks in states... that is why you have to do it in a task-node
I could write a action class for a state.For example:<state name="fire employee"> <transition to="collect badge"> <action class="com.nomercy.hr.RemoveEmployeeUpdate" /> </transition> </state>
In the class RemoveEmployeeUpdate,I could invoke the following code:TaskMgmtInstance.createTaskInstance(...)).
right? I mean that I could write a class to create a task in any node type? -
3. Re: Why should I create task in Task-node ?
kukeltje Jul 15, 2007 1:48 PM (in response to lyo)There is more to a tasknode than just creation of tasks. Look at the implementation of task-node. Not that I do not agree that the border is blurred (i was in favour of not having task-nodes and just add tasks to states. There has to be a mapping to jdpl as well, and there are differences there between state and task.... so it is not that illogical