[exo-jcr-commits] exo-jcr SVN: r4686 - jcr/trunk/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/dataflow/persistent.
do-not-reply at jboss.org
do-not-reply at jboss.org
Thu Jul 28 05:07:13 EDT 2011
Author: tolusha
Date: 2011-07-28 05:07:13 -0400 (Thu, 28 Jul 2011)
New Revision: 4686
Modified:
jcr/trunk/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/dataflow/persistent/CacheableWorkspaceDataManager.java
Log:
EXOJCR-1453: Adoption and testing on all supported DB
Modified: jcr/trunk/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/dataflow/persistent/CacheableWorkspaceDataManager.java
===================================================================
--- jcr/trunk/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/dataflow/persistent/CacheableWorkspaceDataManager.java 2011-07-28 07:36:19 UTC (rev 4685)
+++ jcr/trunk/exo.jcr.component.core/src/main/java/org/exoplatform/services/jcr/impl/dataflow/persistent/CacheableWorkspaceDataManager.java 2011-07-28 09:07:13 UTC (rev 4686)
@@ -51,6 +51,7 @@
import org.exoplatform.services.transaction.TransactionService;
import java.io.Serializable;
+import java.security.PrivilegedAction;
import java.security.PrivilegedActionException;
import java.security.PrivilegedExceptionAction;
import java.util.ArrayList;
@@ -981,7 +982,15 @@
// The listeners will need to be executed outside the current tx so we suspend
// the current tx we can face enlistment issues on product like ISPN
transactionManager.suspend();
- notifySaveItems(logWrapper.getChangesLog(), false);
+
+ SecurityHelper.doPrivilegedAction(new PrivilegedAction<Void>()
+ {
+ public Void run()
+ {
+ notifySaveItems(logWrapper.getChangesLog(), false);
+ return null;
+ }
+ });
// Since the resume method could cause issue with some TM at this stage, we don't resume the tx
}
}
More information about the exo-jcr-commits
mailing list