JBossDeveloper

 

"petemuir" wrote:
Then wire it up

<page view-id="/assignTask.xhtml" action="#{taskFinder.autoStart()}">
 <navigation>
 ...
 </navigation>
</page>

Thanks, sounds good, I'll give it a try.

"petemuir" wrote:
In fact, can you create a JIRA issue for both a task selector and a way of auto-starting tasks - we can probably wrap it up in @CreateProcess / create-process in pages.xml

I'll keep you informed about my progress and will indeed file a feature request -- if only to provide means to document the stuff in the Seam manual ;-)

Thanks,
Arjan.

 

"kukeltje" wrote:
afaik, jBPM 3.2 already is able to do something like autostart

I could only find 16.4.8. task-node, which states:

create-tasks - attribute - optional {yes|no|true|false}, default is true. Can be set to false when a runtime calculation has to determine which of the tasks have to be created. In that case, add an action on node-enter, create the tasks in the action and set create-tasks to false.

end-tasks - attribute - optional {yes|no|true|false}, default is false. In case remove-tasks is set to true, on node-leave, all the tasks that are still open are ended.

However, it defaults to true, according to the quote above, the source code and the XSD:

<xs:element name="task-node">
 <xs:complexType>
 :
 <xs:attribute name="create-tasks" type="booleanType" default="true"/>
 <xs:attribute name="end-tasks" type="booleanType" default="false"/>

So, setting this to true, which it already is, would not make much difference I guess. So: is this what you're referring to?

Thanks,
Arjan.

 

"petemuir" wrote:
Then wire it up

<page view-id="/assignTask.xhtml" action="#{taskFinder.autoStart()}">
 <navigation>
 ...
 </navigation>
</page>

This works great for some process definitions, but I cannot get this to work with sub-processes.

When I start some process that immediately delegates to some sub-process, then a ProcessInstance is injected, but TaskMgmtInstance#getTaskInstances() returns zero elements in the getSingleTaskInstance I posted earlier:

@In ProcessInstance processInstance;

public TaskInstance getSingleTaskInstance() {
 // BEWARE: THIS IS WRONG. This returns all the taskInstances
 // for the process instance, which includes task instances
 // that have already been completed previously.
 Collection<TaskInstance> taskInstances =
 processInstance.getTaskMgmtInstance().getTaskInstances();

 if (taskInstances.size() != 1) {
 log.error("Expected single task, found #0", taskInstances.size());
 return null;
 }
 return taskInstances.iterator().next();
}

So I guess jBPM simply has not created the sub-process yet. Debugging shows that the process instance is indeed the parent process instance at that point.

As for the warning in the code above: I guess I should use getUnfinishedTasks(Token), or discard the finished tasks that getTaskInstances() returns.

Arjan.