[
https://jira.jboss.org/jira/browse/JBPM-2810?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2810:
----------------------------------------
Maybe OpenProcessDefinition should be promoted to the api. There already is a
OpenExecution, OpenProcessInstance. Then this would work:
ProcessDefinitionQuery pdq =
repositoryService.createProcessDefinitionQuery().processDefinitionId(oe.getProcessDefinitionId());
ProcessDefinition pd = pdq.uniqueResult();
System.out.println(((OpenProcessDefinition) pd).getActivities());
Well, it works now as well, but the it is internal....
Wat would be your usecase? If you have an execution and want the active activities, you
can already do that:
OpenExecution oe = (OpenExecution) execution;
Collection< ? > ec = oe.getExecutions();
for (Object object : ec) {
System.out.println(((OpenExecution) object).getActivity());
}
Add API functions to query process definition details (defined tasks,
name of nodes etc)
----------------------------------------------------------------------------------------
Key: JBPM-2810
URL:
https://jira.jboss.org/jira/browse/JBPM-2810
Project: jBPM
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Peter Horvath
It would be great if there were public API methods which provide access to the process
definition - for example to retrieve the name of the tasks defined in a process
definition.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira