[jboss-svn-commits] JBL Code SVN: r36786 - labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US.

[jboss-svn-commits at lists.jboss.org]

Author: kevin.conner at jboss.com
Date: 2011-03-06 13:32:01 -0500 (Sun, 06 Mar 2011)
New Revision: 36786

Modified:
   labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/jBPM_Integration.xml
Log:
Added warning about variable passing between ESB and jBPM: JBESB-3579

Modified: labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/jBPM_Integration.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/jBPM_Integration.xml	2011-03-06 18:25:32 UTC (rev 36785)
+++ labs/jbossesb/branches/JBESB_4_9_CP/product/docs/Services_Guide/en-US/jBPM_Integration.xml	2011-03-06 18:32:01 UTC (rev 36786)
@@ -883,6 +883,15 @@
         Service Bus is asynchronous in nature and, therefore, does not block
         the process instance whilst the service executes.
     </para>
+    <warning>
+        <para>
+            It is important that the classes representing any of the variables passing
+            between jBPM and JBoss ESB services must be visible to the jBPM process, target ESB
+            services and the ESB jBPM callback service.  For this reason the recommended
+            practice is to deploy these classes into the server's <filename>lib</filename>
+            directory.
+        </para>
+    </warning>
         
     <para>
         The <classname>EsbNotifier</classname> will be examined first, as it