I'm currently working in a jbpm3.1.3 environment. I have run into an unexplained behavior with the create-tasks attribute of the task-node element.
In a process definition where task-nodes do NOT contain this attribute, instantiating a new process instance and task instances, then signalling the processinstance, works as expected. It reaches the end state and creates new taskinstances along the way. In a process definition where task-nodes DO contain this attribute, instantiating a new process instance and task instances, then signalling the processinstance, does not work as expected. It ignores the transitons included in the signal and takes the default transition for every task node. The only difference is the addition of the create-tasks attribute using the eclipse plugin. Any and all ideas, suggestions, or criticisms are welcome. dhw View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071736#4071736 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071736 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
