jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (JCR-3745) Add JackrabbitObservationManager with additional methods for registering event listeners
Date Thu, 13 Mar 2014 12:37:43 GMT

    [ https://issues.apache.org/jira/browse/JCR-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933181#comment-13933181

Michael Dürig commented on JCR-3745:

bq. I think we can just keep both methods and should be fine.

But then

addEventListener(listener, (EventFilter)filter);

would suddenly call the "wrong" method once {{ObservationManager}} is JCR 2.1. This is not
a problem if we are fine with giving that method also the extended semantics. So the questions
burns down to: should the extended functionality go into {{ObservationManager.addEventListener()}}
or only be available in {{JackrabbitObservationManager.addEventListener()}} once JCR 2.1 is
out? The former does bend the spec somewhat but would allow us to @deprecate {{JackrabbitObservationManager}}
at that time.

bq. JackrabbitEventListener as a final class? 

Class yes, final why? 

> Add JackrabbitObservationManager with additional methods for registering event listeners
> ----------------------------------------------------------------------------------------
>                 Key: JCR-3745
>                 URL: https://issues.apache.org/jira/browse/JCR-3745
>             Project: Jackrabbit Content Repository
>          Issue Type: New Feature
>          Components: jackrabbit-api
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>         Attachments: JCR-3745.patch
> I'd like to add an additional method for adding event listeners to the Jackrabbit API:

> void addEventListener(EventListener listener, int eventTypes, String[] absPaths, boolean
isDeep, String[] uuid, String[] nodeTypeName, boolean noLocal, boolean noExternal) throws
> Compared to the JCR method of the same name, this method takes an array of absPath and
additional boolean argument: 
> Only events whose associated parent node is at one of the paths in <code>absPaths</code>
(or within its subgraph, if <code>isDeep</code> is <code>true</code>)
will be received. 
> and 
> Additionally, if <code>noExternal</code> is <code>true</code>,
then events from external cluster nodes are ignored. Otherwise, they are not ignored.

This message was sent by Atlassian JIRA

View raw message