[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...
]
Sebastian Schneider commented on JBPM-2771:
-------------------------------------------
Reading through the section async executions in the documentation I was just wondering how
to start a process without blocking the client. It came to my mind that this should be
possible via the API without the need to specifiy this in the process defnition
explicitly. So additional to fixing this does it make sense to provide a
startProcessInstance() -method enabling users to start process definitions in a
non-blocking way (= not in the client thread)?
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