Jukka Zitting wrote:
Hi,
On Tue, Jul 22, 2008 at 12:10 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
In both cases I'm generating application events out of the observation
events, like a page has changed event, removed etc. The post processing is
actually done based on this application events, so if a page has changed,
some action is started. Therefore my application events need to be marked as
local as well.
Ah, I see. Then I guess we really do need the isLocal() (or
isExternal() as suggested by Toby) method.
Perhaps we should reopen JCR-1672 and revert the LocalEventListener
changes, as I'd rather not have two overlapping mechanisms for the
same functionality.
Hmm, yes, I guess that's the best - although the interface approach is
a nicer way of handling this *if* you only need the local changes (it's
easier to implement for a client and optimizes event notification a
little bit).
I'll come up with a patch.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
