[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... ] Darrin Mison commented on JBPM-2327: ------------------------------------ Other two items updated in SOA jBPM guide as: <para> But 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="true"</literal>. <literal>async="true"</literal> is supported only when it is triggered in an event but can be specified on all node types and all action types. </para> <entry> <literal>'async="true"</literal> is only supported in <classname>action</classname> when it is triggered in an event. The default value is <literal>false</literal>, which means that the <classname>action</classname> is executed in the thread of the execution. If set to <literal>true</literal>, a message will be sent to the command executor and that component will execute the action asynchronously in a separate transaction. </entry> -- 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