-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Core
-
Tags:
-
Sprint:nxplatform 11.1.15
-
Story Points:2
Since NXP-24359, we can now lock twice a document without error.
The test TestSQLRepositoryAPI.testLocking has been updated to reflect this change but it has been failing on MongoDB since, see:
java.lang.AssertionError: expected:<org.nuxeo.ecm.core.api.Lock@6e009215> but was:<org.nuxeo.ecm.core.api.Lock@364a1b2f> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:144) at org.nuxeo.ecm.core.TestSQLRepositoryAPI.testLocking(TestSQLRepositoryAPI.java:4369)
Issue is probably just the lack of equals implementation in Lock and it's not visible on VCS because VCSLockManager has a cache and so we get the same object.
- is caused by
-
NXP-24359 Document.Lock called twice should not fail
- Resolved