[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2327) Docs on asynchronous continuations are misleading
[
https://jira.jboss.org/jira/browse/JBPM-2327?page=com.atlassian.jira.plug...
]
Alejandro Guizar commented on JBPM-2327:
----------------------------------------
One more addition to 16.4.17: the script element supports the async attribute as well.
http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP02/html/JBPM_Re...
<row>
<entry>async</entry>
<entry>attibute</entry>
<entry>{true|false}</entry>
<entry>defaults to false, meaning that the script is executed in the
current
thread. If set to true, a job will be posted and the executor component
will run the script in a separate transaction.
</entry>
</row>
Docs on asynchronous continuations are misleading
-------------------------------------------------
Key: JBPM-2327
URL: https://jira.jboss.org/jira/browse/JBPM-2327
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: jBPM 3.2.5.SP5
Reporter: Martin Putz
Assignee: Darrin Mison
Chapter 4.3.4 of the User Guide states:
There are 3 places where execution can be continued asynchronously:
* Just before the node's execute method. Which is after entering the node.
* When execution is about to be propagated over a transition. Which is before leaving
a node.
* Every action can be executed asynchonously as well.
http://docs.jboss.org/jbpm/v3.2/userguide/html/graphorientedprogramming.h...
Only the first case is implemented, therefore the docs should be cleaned up and the other
points removed.
--
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