Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <30542276.1164061445435.JavaMail.jira@brutus>
Date: Mon, 20 Nov 2006 14:24:05 -0800 (PST)
From: "Paco Avila (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-641) can't add lock token to session after 3
 login/logout
In-Reply-To: <7454072.1164061322378.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/JCR-641?page=all ]

Paco Avila updated JCR-641:
---------------------------

    Attachment: repository2.xml

> can't add lock token to session after 3 login/logout
> ----------------------------------------------------
>
>                 Key: JCR-641
>                 URL: http://issues.apache.org/jira/browse/JCR-641
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: locks
>    Affects Versions: 1.1
>         Environment: Linux Ubuntu Dapper
>            Reporter: Paco Avila
>            Priority: Critical
>         Attachments: DummyLockToken.java, repository2.xml
>
>
> I login and lock a file and logout. Perfoms a new login and add the previous lock token to the current session because I want to unlock this file. This works fine. But if I do a new logout/login I can't unlock the file (the file is locked). It is best understanded looking at the test case.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira