[
https://jira.jboss.org/jira/browse/JBPM-2758?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2758:
----------------------------------------
The reason is that the processdefinition is null in the execution where the
assignmenthandler for the task after the join is initialized in ExecutionImpl. The
processinstance id is not null, so adding an additional 'getProcessDefinition()'
only when the definition is null solves the issue. Might need additional investigation why
it is null, but the fix can be included I think.
NPE on assignmenthandler when using fork/join
---------------------------------------------
Key: JBPM-2758
URL:
https://jira.jboss.org/jira/browse/JBPM-2758
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Reporter: Ronald van Kuijk
Assignee: Ronald van Kuijk
Fix For: jBPM 4.4
When using swimalanes on tasks within a fork/join construct and having a task with a
swimlane after the join, an NPE is thrown. For details see the forum.
--
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