Return-Path: X-Original-To: apmail-jackrabbit-dev-archive@www.apache.org Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 72B94106EA for ; Thu, 13 Mar 2014 12:58:01 +0000 (UTC) Received: (qmail 20700 invoked by uid 500); 13 Mar 2014 12:57:50 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 19872 invoked by uid 500); 13 Mar 2014 12:57:47 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 19790 invoked by uid 99); 13 Mar 2014 12:57:44 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Mar 2014 12:57:44 +0000 Date: Thu, 13 Mar 2014 12:57:44 +0000 (UTC) From: "Felix Meschberger (JIRA)" To: dev@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (JCR-3745) Add JackrabbitObservationManager with additional methods for registering event listeners MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/JCR-3745?page=3Dcom.atlassian.j= ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D139331= 97#comment-13933197 ]=20 Felix Meschberger commented on JCR-3745: ---------------------------------------- bq. Class yes, final why?=20 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 expose= d in this base class. If we later see, that extension makes sense we can st= ill make it non-final. But making a non-final class final is essentially ki= lling 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=C3=BCrig > Assignee: Michael D=C3=BCrig > Attachments: JCR-3745.patch > > > I'd like to add an additional method for adding event listeners to the Ja= ckrabbit API:=20 > void addEventListener(EventListener listener, int eventTypes, String[] ab= sPaths, boolean isDeep, String[] uuid, String[] nodeTypeName, boolean noLoc= al, boolean noExternal) throws RepositoryException;=20 > Compared to the JCR method of the same name, this method takes an array o= f absPath and additional boolean argument:=20 > Only events whose associated parent node is at one of the paths in = absPaths (or within its subgraph, if isDeep is tr= ue) will be received.=20 > and=20 > Additionally, if noExternal is true, then event= s from external cluster nodes are ignored. Otherwise, they are not ignored. -- This message was sent by Atlassian JIRA (v6.2#6252)