Author: nfilotto Date: 2010-01-21 09:48:20 -0500 (Thu, 21 Jan 2010) New Revision: 1531 Modified: jcr/trunk/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/core/query/jbosscache/JBossCacheIndexInfos.java Log: EXOJCR-423: Manage the case the node already exists in JBossCacheIndexInfos Modified: jcr/trunk/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/core/query/jbosscache/JBossCacheIndexInfos.java =================================================================== --- jcr/trunk/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/core/query/jbosscache/JBossCacheIndexInfos.java 2010-01-21 14:39:48 UTC (rev 1530) +++ jcr/trunk/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/core/query/jbosscache/JBossCacheIndexInfos.java 2010-01-21 14:48:20 UTC (rev 1531) @@ -108,6 +108,10 @@ cache.getInvocationContext().getOptionOverrides().setCacheModeLocal(true); cacheRoot.addChild(namesFqn).setResident(true); } + else + { + cache.getNode(namesFqn).setResident(true); + } if (modeHandler.getMode() == IndexerIoMode.READ_ONLY) { // Currently READ_ONLY is set, so new lists should be fired to multiIndex.