[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2771) continue=async on <start> causes NullPointerException
[
https://jira.jboss.org/jira/browse/JBPM-2771?page=com.atlassian.jira.plug...
]
Ronald van Kuijk commented on JBPM-2771:
----------------------------------------
Thanks for the testcase...
After a lot (really, a lot, 4 hours) of writing a testcase, puzzeling, debugging, step by
step, I came to the conclusion that this can be solved by adding a
name='whateverValueYouChoose' attribute to the start node.
The reason for this is that jobExecutor does not get an activity when there no name is
specified and hence the NPE, so probably the timer creator needs this.
I think the description should be changed that IF there is a continue = 'async', a
name should be required and the parsing fails if it is not there. In other nodes you
cannot omit a name since transitions have to point to it.
We couldcould also change the name attribute to be REQUIRED (Tom B, if you read this ;-))
continue=async on <start> causes NullPointerException
-----------------------------------------------------
Key: JBPM-2771
URL: https://jira.jboss.org/jira/browse/JBPM-2771
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Any
Reporter: Martin Porter
Adding continue="async" on a <start> of a process will cause a
NullPointerException when you attempt to start the process. We need this to prevent the
caller waiting when the process instance is created but it does not work. Currently we use
a workaround to call a <java> activity which prints a message to the log and does
the async continuation.
--
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