[
https://jira.jboss.org/jira/browse/JBPM-2643?page=com.atlassian.jira.plug...
]
Sebastian Schneider updated JBPM-2643:
--------------------------------------
Affects Version/s: jBPM 4.1
Description:
Creating tasks in a user's task list not belonging to an execution breaks the console.
For example:
Task task = taskService.createTask();
task.setName("name ..");
task.setAssignee("assignee ..");
taskService.save(task);
After the creation the jbpm-console breaks and can't display tasks of this user
anymore. An exception is then thrown telling that the executionId is null. I consider this
a bug since there can be tasks not belonging to an execution.
Could anybody verify if this bug persists in jBPM 4.2?
was:
Creating tasks in a user's task list not belonging to an execution breaks the console.
For example:
[code]
Task task = taskService.createTask();
task.setName("name ..");
task.setAssignee("assignee ..");
taskService.save(task);
[/code]
After the creation the jbpm-console breaks and can't display tasks of this user
anymore. An exception is then thrown telling that the executionId is null. I consider this
a bug since there can be tasks not belonging to an execution.
Could anybody verify if this bug persists in jBPM 4.2?
adding tasks not belonging to an execution breaks the console
-------------------------------------------------------------
Key: JBPM-2643
URL:
https://jira.jboss.org/jira/browse/JBPM-2643
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Console
Affects Versions: jBPM 4.1
Environment: not relevant
Reporter: Sebastian Schneider
Fix For: jBPM 4.3
Creating tasks in a user's task list not belonging to an execution breaks the
console. For example:
Task task = taskService.createTask();
task.setName("name ..");
task.setAssignee("assignee ..");
taskService.save(task);
After the creation the jbpm-console breaks and can't display tasks of this user
anymore. An exception is then thrown telling that the executionId is null. I consider this
a bug since there can be tasks not belonging to an execution.
Could anybody verify if this bug persists in jBPM 4.2?
--
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