[jbpm-commits] JBoss JBPM SVN: r3592 - jbpm3/trunk/modules/core/src/main/java/org/jbpm/command.

[do-not-reply at jboss.org]

Author: camunda
Date: 2009-01-07 08:10:16 -0500 (Wed, 07 Jan 2009)
New Revision: 3592

Modified:
   jbpm3/trunk/modules/core/src/main/java/org/jbpm/command/ChangeProcessInstanceVersionCommand.java
Log:
added comment on possible problems with ESB integration after version changing (see http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200079)

Modified: jbpm3/trunk/modules/core/src/main/java/org/jbpm/command/ChangeProcessInstanceVersionCommand.java
===================================================================
--- jbpm3/trunk/modules/core/src/main/java/org/jbpm/command/ChangeProcessInstanceVersionCommand.java	2009-01-07 11:07:22 UTC (rev 3591)
+++ jbpm3/trunk/modules/core/src/main/java/org/jbpm/command/ChangeProcessInstanceVersionCommand.java	2009-01-07 13:10:16 UTC (rev 3592)
@@ -39,13 +39,17 @@
  *        {@link TaskInstance} exists, the {@link Task} definition must
  *        exist in the {@link TaskNode} with the same (or mapped) name.
  *        Otherwise the right node cannot be found easily because it may be
- *        ambiguous.
+ *        ambiguous.</li>
  *   <li> Sub processes aren't yet tested. Since the {@link ProcessState} is 
- *        a {@link Node} like any other, it should work anyway.
+ *        a {@link Node} like any other, it should work anyway.</li>
  *   <li> Can have <b>negative impact on referential integrity</b>! Because
  *        one {@link ProcessInstance} can have {@link ProcessLog}s point to
  *        old {@link ProcessDefinition}s. Hence, delete a {@link ProcessDefinition}
- *        may not work and throw an Exception (Integrity constraint violation)  
+ *        may not work and throw an Exception (Integrity constraint violation)</li>  
+ *   <li> In combination with ESB the ESB uses {@link Token}.id <b>and</b> {@link Node}.id
+ *        as correlation identifier. After changing the version of a {@link ProcessInstance}
+ *        the {@link Node}.id has changed, so a signal from ESB will result in an exception
+ *        and has to be corrected manually.</li>
  * </ul>
  * 
  * @author Bernd Ruecker (bernd.ruecker at camunda.com)