[
https://issues.apache.org/jira/browse/JCR-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13933197#comment-13933197
]
Felix Meschberger commented on JCR-3745:
----------------------------------------
bq. Class yes, final why?
What's the use of extending it ? The ObservationManager is the consumer of the
instance and it can only support what it can support and thus is exposed in
this base class. If we later see, that extension makes sense we can still make
it non-final. But making a non-final class final is essentially killing
backwards compatibility.
> 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 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)