SWF-360 Update docs for flow managed persistence propagation
This commit is contained in:
@@ -75,4 +75,14 @@
|
||||
Such data access operations should always execute non transactionally or in read-only transactions to maintain isolation of intermediate edits.
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1 id="flow-managed-persistence-propagation">
|
||||
<title>Flow Managed Persistence And Sub-Flows</title>
|
||||
<para>
|
||||
Starting with version 2.3 a flow managed <code>PersistenceContext</code> is automatically extended
|
||||
(propagated) to subflows assuming the subflow also has the <code><perstistence-context/></code>
|
||||
variable. When a subflow re-uses the <code>PersistenceContext</code> started by its parent it ignores
|
||||
commit flags when an end state is reached thereby deferring the final decision (to commit or not) to
|
||||
its parent.
|
||||
</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
Reference in New Issue
Block a user