jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JCR-3015) EntryCollector may log warning for inexistent item
Date Thu, 07 Jul 2011 10:11:16 GMT

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

Marcel Reutegger resolved JCR-3015.

       Resolution: Fixed
    Fix Version/s: 2.3.0

Fixed in trunk in revision: 1143738 and merged into 2.2 branch in revision: 1143747

> EntryCollector may log warning for inexistent item
> --------------------------------------------------
>                 Key: JCR-3015
>                 URL: https://issues.apache.org/jira/browse/JCR-3015
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 2.2.8, 2.3.0
> Currently the EntryCollector may log a warning when the node reported in the event does
not exist. This may happen when the repository runs in a cluster and a node is created and
immediately removed again. This issue is related to JCR-3014. The call to Session.nodeExists()
should actually return false when the identifier path cannot be resolved. Currently it throws
a RepositoryException.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message