[
https://issues.apache.org/jira/browse/JCR-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932542#comment-13932542
]
Robert Munteanu commented on JCR-3745:
--------------------------------------
Hm, good point. I'm not sure if it's possible to just 'inline' the JSR-333 API
in the JackrabbitEventFilter and then when JSR-333 is out retrofit it to
implement the interface. It would definitely work for new clients, but I'm
concerned about clients migrating from the pre-JSR-333 API to the new one...
> 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)
