Author: nzamosenchuk
Date: 2010-02-15 09:11:20 -0500 (Mon, 15 Feb 2010)
New Revision: 1822
Modified:
jcr/trunk/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/dataflow/persistent/jbosscache/ParentNodeEvictionActionPolicy.java
Log:
EXOJCR-507: Fix committed. Need to use PEEK instead of getNode
Modified:
jcr/trunk/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/dataflow/persistent/jbosscache/ParentNodeEvictionActionPolicy.java
===================================================================
---
jcr/trunk/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/dataflow/persistent/jbosscache/ParentNodeEvictionActionPolicy.java 2010-02-15
11:22:21 UTC (rev 1821)
+++
jcr/trunk/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/dataflow/persistent/jbosscache/ParentNodeEvictionActionPolicy.java 2010-02-15
14:11:20 UTC (rev 1822)
@@ -78,7 +78,7 @@
// We use the method getChildrenNamesDirect to avoid going through
// the interceptor chain (EXOJCR-460)
- Set<Object> names =
((CacheSPI)cache).getNode(parentFqn).getChildrenNamesDirect();
+ Set<Object> names = ((CacheSPI)cache).peek(parentFqn,
false).getChildrenNamesDirect();
if (names.isEmpty() || (names.size() == 1 &&
names.contains(fqn.get(2))))
{
if (log.isTraceEnabled())