Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <31674954.1193142770704.JavaMail.jira@brutus>
Date: Tue, 23 Oct 2007 05:32:50 -0700 (PDT)
From: "Marcel Reutegger (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-1179) Event filtering by path not working as
 specified
In-Reply-To: <355614.1192703690568.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Marcel Reutegger updated JCR-1179:
----------------------------------

    Affects Version/s: 1.0
                       1.0.1
                       1.1
                       1.1.1
                       1.2.1
                       1.2.2
                       1.2.3
                       1.3
                       1.3.1
                       1.3.3

+1 I agree, this should be fixed asap.

> Event filtering by path not working as specified
> ------------------------------------------------
>
>                 Key: JCR-1179
>                 URL: https://issues.apache.org/jira/browse/JCR-1179
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: observation
>    Affects Versions: 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.3, 1.=
3.1, 1.3.3
>            Reporter: Julian Reschke
>            Assignee: Marcel Reutegger
>         Attachments: JCR-1179.patch
>
>
> When filtering node events by path, the event filter doesn't compare usin=
g the "associated parent path", see JSR-170, 8.3.3:
> "The set of events can be filtered by specifying restrictions based on ch=
aracteristics of the associated parent node of the event. The associated pa=
rent node of an event is the parent node of the item at (or formerly at) th=
e path returned by Event.getPath. The following restrictions are available:
> =E2=80=A2 absPath, isDeep: Only events whose associated parent node is at=
 absPath (or within its subtree, if isDeep is true) will be received. It is=
 permissible to register a listener for a path where no node currently exis=
ts."
> (for property events, filtering is correct)
> To fix this, the special handling of node events in EventFilter.blocks() =
simply needs to be removed.

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