jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1361) Lock test assumes that changes in one session are immediately visible in different session
Date Wed, 05 Mar 2008 15:35:40 GMT

     [ https://issues.apache.org/jira/browse/JCR-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jukka Zitting updated JCR-1361:
-------------------------------

    Fix Version/s: 1.5

> Lock test assumes that changes in one session are immediately visible in different session
> ------------------------------------------------------------------------------------------
>
>                 Key: JCR-1361
>                 URL: https://issues.apache.org/jira/browse/JCR-1361
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-jcr-tests
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Minor
>             Fix For: 1.5
>
>
> 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());

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message