[JCR-1361] Lock test assumes that changes in one session are immediately visible in different session

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.5
• Component/s: jackrabbit-jcr-tests
• Assignee: Julian Reschke
• Reporter: Julian Reschke
• Created: 05/Feb/08 21:09
• Updated: 08/Dec/08 11:09
• Resolved: 06/Feb/08 11:21

Description

LockTest.testLogout() assumes that a change in one session (logging out, removing a session-scoped lock) is immediately visible in another session.

Proposal: insert a

n1.getSession().refresh(true);

call before checking

assertFalse("node must not be locked", n1.isLocked());

Issue Links

• relates to: JCR-774 TCK: Test that expect that modifications made by Session1 are automatically visible to Session2