-
Bug
-
Resolution: Done
-
Blocker
-
3.1.2.Final
-
None
The following code will work with DummyTransacationManager but not real JTA transaction manager (Atomisk)
@Transactional
public void createNewNode(JCRSessionHolder sessionHolder) throws ItemExistsException, PathNotFoundException, NoSuchNodeTypeException, LockException, VersionException, ConstraintViolationException, RepositoryException {
VersionManager vm = sessionHolder.getSession().getWorkspace().getVersionManager();
Node node = sessionHolder.getSession().getRootNode().addNode("Test3", "pd:product");
node.addMixin("mix:versionable");
node.setProperty("name", "lalalal");
node.setProperty("code", "lalalal");
sessionHolder.getSession().save();
vm.checkin(node.getPath());
}
Exception in thread "main" javax.jcr.InvalidItemStateException: This operation cannot be performed when the session has pending changes
at org.modeshape.jcr.JcrVersionManager.checkin(JcrVersionManager.java:321)
at org.modeshape.jcr.JcrVersionManager.checkin(JcrVersionManager.java:304)
at JTATest$JCRTest.createNewNode(JTATest.java:76)
at JTATest.main(JTATest.java:56)
For VersionManager.checkout, if I call it in the beginning of the method and then make some change to the node, and save(), ModeShape will complain the node is not checkout.
- incorporates
-
MODE-1862 "java.lang.IllegalStateException: This is a tx cache!" when using federation
-
- Closed
-
- is related to
-
MODE-1819 Session.move() fails when using user transactions
-
- Closed
-
-
MODE-1837 Sometimes query returns duplicated records after commiting a transaction that contains VersionManager.checkin() call when using a real JTA transaction manager
-
- Closed
-
- relates to
-
MODE-1854 Indexing took too much time to finish when using explicit JTA transaction compared to no transaction
-
- Closed
-