Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <20645448.1153405155025.JavaMail.jira@brutus>
Date: Thu, 20 Jul 2006 07:19:15 -0700 (PDT)
From: "Tobias Bocanegra (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Closed: (JCR-486) Removed version is not invalidated
In-Reply-To: <753032.1153395014908.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-486?page=all ]

Tobias Bocanegra closed JCR-486.
--------------------------------

    Resolution: Fixed

Committed revision 423943.


> Removed version is not invalidated
> ----------------------------------
>
>                 Key: JCR-486
>                 URL: http://issues.apache.org/jira/browse/JCR-486
>             Project: Jackrabbit
>          Issue Type: Bug
>    Affects Versions: 1.0.1, 1.1
>            Reporter: Tobias Bocanegra
>         Assigned To: Tobias Bocanegra
>
> when a version is removed, it's internal represenation is not evicted from the cache. this can leed to unexpected behaviours. XATest.removeVersion() tests this. this also happens in a non-transactional environment.

-- 
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