[
https://jira.jboss.org/jira/browse/JBPM-2327?page=com.atlassian.jira.plug...
]
Alejandro Guizar reassigned JBPM-2327:
--------------------------------------
Assignee: Darrin Mison (was: Alejandro Guizar)
Darrin, let me suggest one more edit to make the user guide completely accurate.
<para>
However, in some situations a developer might want to fine-tune the transaction
demarcation in the
process definition. In jPDL, it is possible to specify that the process execution should
continue asynchronously with the attribute <literal>async</literal> set to
<literal>true</literal>.
Attribute <literal>async</literal> can be specified on all node types. Action
types
<literal>action</literal>, <literal>script</literal> and
<literal>mail</literal> support
the <literal>async</literal> attribute, but only when acting as event
listeners. For actions and
scripts used as node behavior, the node itself can be made asynchronous.
</para>
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