anonymous wrote : but what they do are almost same. so i want to do it in one task-node, as co-signing does. If difficult to implement, i will change it to one person one task-node. Is it the correct way?
Again... you say you *want* it, but what is the process requirement...AND you say *almost* the same... then it is definitely not the the same task. What you could try (but then you hide the sequence/parallel) stuff in code (which I do strongly advise against, since you could as well create all task individually via the api from plain javacode) is to not create all tasks at the same moment. but if one task finishes, on the task-end event create another task for someone new.... Again this is really dirty and I would not use a processdefinition for this but the api on a low level anonymous wrote : I read JBPM doc, but i cant get any useful stuff in such situation. | Could you tell me more? Because what you want to do is dirty, uncommon, error-prone, hides 'flow' in javacode etc.... But I was not talking about this specific co-signing thing, I was talking about the fact that you could not see you could place a subprocess or something else in the foreachforkhandler.... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4197413#4197413 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4197413 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
