5 Replies Latest reply on Nov 13, 2009 3:13 AM by Sebastian Schneider

    Tasks not belonging to an execution

    Sebastian Schneider Master

      I created several tasks not belonging to an execution which worked fine using the API:

      Task task = taskService.createTask();
      task.setName("name ..");
      task.setAssignee("assignee ..");
      taskService.save(task);
      


      But afterwards the jbpm-console breaks and can't display tasks 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. If there is no opposition I'm going to fill an JIRA issue.