[ https://issues.apache.org/jira/browse/OAK-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated OAK-2747: ---------------------------------- Fix Version/s: 1.2.3 Merged fix into 1.2 branch: http://svn.apache.org/r1686788 > Admin cannot create versions on a locked page by itself > ------------------------------------------------------- > > Key: OAK-2747 > URL: https://issues.apache.org/jira/browse/OAK-2747 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: core, jcr > Affects Versions: 1.2.1 > Reporter: Marius Petria > Assignee: Marcel Reutegger > Fix For: 1.3.1, 1.2.3 > > Attachments: > 0001-Fix-unchecked-conversion-warnings-in-VersionManagerI.patch, > 0002-Fix-unchecked-conversion-warnings-in-LockManagerImpl.patch, > 0003-OAK-2747-Admin-cannot-create-versions-on-a-locked-pa.patch > > > Admin cannot create versions even if it is the lockowner. > This is a test to go in VersionManagementTest that shows the issue. > The general questions are: > - should de lockowner be able to create versions? > - should admin be able to create versions even if it is not the lockowner? > {code} > @Test > public void testCheckInCheckoutLocked() throws Exception { > Node n = createVersionableNode(superuser.getNode(path)); > n.addMixin(mixLockable); > superuser.save(); > n = superuser.getNode(n.getPath()); > n.lock(true, false); > testSession.save(); > n = superuser.getNode(n.getPath()); > n.checkin(); > n.checkout(); > } > {code} > fails with > {noformat} > javax.jcr.lock.LockException: Node at /testroot/node1/node1 is locked > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)