[
https://issues.apache.org/jira/browse/JCR-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933092#comment-13933092
]
Michael Dürig commented on JCR-3745:
------------------------------------
bq. I like the filter idea, but...
Unfortunately that's what made its way into JCR2.1 for whatever reason...
Apart from that what we could do to be forward compatible with {{EventFilter}}
from upcoming JCR 2.1 is to declare a {{JackrabbitEventFilter}} copying all the
methods from {{EventFilter}} over. Once JCR 2.1 is out, we could drop those
methods again and make {{JackrabbitEventFilter extends EventFilter}}. I'll give
this a shot.
> 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
>
> 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 RepositoryException;
> 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
(v6.2#6252)
