[jbpm-commits] JBoss JBPM SVN: r5659 - jbpm4/trunk/modules/userguide/src/main/docbook/en/modules.

do-not-reply at jboss.org do-not-reply at jboss.org
Thu Sep 17 12:06:37 EDT 2009


Author: jbarrez
Date: 2009-09-17 12:06:37 -0400 (Thu, 17 Sep 2009)
New Revision: 5659

Modified:
   jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch06-Jpdl.xml
Log:
Enhanced explanation of threadsafe notion of user code

Modified: jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch06-Jpdl.xml
===================================================================
--- jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch06-Jpdl.xml	2009-09-17 12:58:19 UTC (rev 5658)
+++ jbpm4/trunk/modules/userguide/src/main/docbook/en/modules/ch06-Jpdl.xml	2009-09-17 16:06:37 UTC (rev 5659)
@@ -2900,8 +2900,11 @@
       <listitem><literal>handler</literal> in decision</listitem>
     </itemizedlist>
     <para>For all objects that are referenced by a class name, will be  
-    instantiated during parsing time.  Which implies that the objects have to be 
-    threadsafe.  This is typically OK since those objects are typically immutable. 
+    instantiated during parsing time.  Which implies that the objects aren't
+    allowed to store non-stateless data (ie which can change).
+    This is typically OK since those objects are in practice almost always immutable. 
+    If you do need to use 'dynamic' data in your user code, you can always 
+    fall back to process variables (or Environment.get(xxx) calls).
     </para>
     <para>Objects that are referenced by an expression are calculated 
     dynamically.



More information about the jbpm-commits mailing list