This content has been marked as final.
Show 4 replies
-
1. Re: Transition for one node to another
mputz May 23, 2007 9:54 AM (in response to vedavyas)What needs to be done?
Read the docu!?
see http://docs.jboss.com/jbpm/v3/userguide/processmodelling.html#nodetypenode:
The type node serves the situation where you want to write your own code in a node. The nodetype node expects one subelement action. The action is executed when the execution arrives in the node. The code you write in the actionhandler can do anything you want but it is also responsible for propagating the execution. -
2. Re: Transition for one node to another
vedavyas May 23, 2007 10:30 AM (in response to vedavyas)Yes i had tried it before. But if i do in this way it leads to one more issue. Suppose a particular actor has a more than one task in his tasklist, whichever task he first assigns, only that instance goes through both the nodes.
All the other tasks are lost after it is assigned -
3. Re: Transition for one node to another
estaub May 23, 2007 11:51 AM (in response to vedavyas)Vedavyas,
You wrote:Suppose a particular actor has a more than one task in his tasklist, whichever task he first assigns, only that instance goes through both the nodes.
I don't think you're being clear enough about what you're trying to do for anyone to help you. Please put yourself in our shoes when you write, and think about what we couldn't possibly guess at. In this case, I'm reading your note as if you want something crazy that I won't even bother to explain - you probably don't, but I can't tell!
-Ed Staub -
4. Re: Transition for one node to another
kukeltje May 23, 2007 1:10 PM (in response to vedavyas)in 3.1 default behaviour of node was to continue
in 3.2 default behaviour of node changed to 'wait'
So your action has to tell the nod to continue on a transition