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-2075) JSR 283: Identifier based event filtering
Date Wed, 15 Apr 2009 20:17:15 GMT

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

Marcel Reutegger resolved JCR-2075.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.6.0

Interestingly enough, this is already working...

Jackrabbit does not check if the node to be filtered is actually mix:referenceable, it just
compares the given UUIDs. Which is what the new behaviour is in JSR 283.

Added test case in revision: 765337

> JSR 283: Identifier based event filtering
> -----------------------------------------
>
>                 Key: JCR-2075
>                 URL: https://issues.apache.org/jira/browse/JCR-2075
>             Project: Jackrabbit Content Repository
>          Issue Type: Sub-task
>            Reporter: Marcel Reutegger
>             Fix For: 1.6.0
>
>
> JSR 283 PFD states:
> Only events whose associated parent node has one of the identifiers in the uuid String
array will be received. If this parameter is null then no identifier-related restriction is
placed on events received. Note that specifying an empty array instead of null results in
no nodes being listened to. The uuid is used for backwards compatibility with JCR 1.0.

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