]
Alejandro Guizar updated JBPM-2977:
-----------------------------------
Fix Version/s: jBPM 4.x
NPE in HistoryActivityInstanceImpl ctor when Activity is null
-------------------------------------------------------------
Key: JBPM-2977
URL:
https://jira.jboss.org/browse/JBPM-2977
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.4
Reporter: Mike M
Fix For: jBPM 4.x
In 4.4, automatic history recording was added for custom activities (JBPM-2495). In order
to work around (JBPM-2976), we had to create a custom activity that was basically the
ForkActivity with slight modification. In the jbpm implementation of the ForkActivity (on
which ours was based), it sets the Activity of the root execution to null before launching
child executions. When the process engine later executes the history code, the constructor
for HistoryActivityInstanceImpl fails with an NPE because the activity is null.
Our workaround is to comment out the line in our Fork implementation that sets the
Activity to null. Not sure if this has any side effects, but we haven't seen any so
far.
Now granted, it is a rather odd case to have a custom activity setting the activity to
null. But nonetheless, it seems that a generic history mechanism should handle this case
gracefully, rather than just throwing an NPE.
Our
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: