From 94be1ad1cce85fe58fa13d9957dccd1ab8facae0 Mon Sep 17 00:00:00 2001 From: Boris Bendyukov Date: Fri, 17 Jan 2014 11:26:34 +0000 Subject: [PATCH] CorrelationVal.java edited online with Bitbucket --- .../jbi/engine/bpel/core/bpel/engine/impl/CorrelationVal.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ojc-core/bpelse/bpelcore/src/com/sun/jbi/engine/bpel/core/bpel/engine/impl/CorrelationVal.java b/ojc-core/bpelse/bpelcore/src/com/sun/jbi/engine/bpel/core/bpel/engine/impl/CorrelationVal.java index b45bf78bb..81cd2ee72 100755 --- a/ojc-core/bpelse/bpelcore/src/com/sun/jbi/engine/bpel/core/bpel/engine/impl/CorrelationVal.java +++ b/ojc-core/bpelse/bpelcore/src/com/sun/jbi/engine/bpel/core/bpel/engine/impl/CorrelationVal.java @@ -43,7 +43,7 @@ import com.sun.wsdl4j.ext.bpel.MessagePropertyAlias; * As per the BPEL specifcation, the correlation value would be * {valueOfProp1}{valueOfProp2}....{valueOfLastProp}. To facilitate, support * of correlations that are totally unrelated to each other but end up - * having the same ID, a prefix of “valueOfCorrelationSetUniqueID” is added. + * having the same ID, a prefix of "valueOfCorrelationSetUniqueID" is added. * ValueOfCorrelationSetUniqueID is preferred to the * valueOfCorrelationSetName because of the possibility of overloaded names * in the same BPEL within scopes. When the model is parsed, each @@ -52,7 +52,7 @@ import com.sun.wsdl4j.ext.bpel.MessagePropertyAlias; * * Extending the same reasoning further, to differentiate CorrelationIDs * across different BPELs within the same engine, the ID is suffixed with - * the “uniqueIDof BPEL”. This plays an important role in the design for + * the "uniqueIDof BPEL". This plays an important role in the design for * recovery. Since the engine uses one persistenceStore, all the * correlationIDs across BPEL instances are stored in the same table. *