jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1672) Adding Event interface and isLocal()
Date Fri, 25 Jul 2008 12:37:31 GMT

    [ https://issues.apache.org/jira/browse/JCR-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616877#action_12616877

Jukka Zitting commented on JCR-1672:

Also, I reverted the original patch (revision 677261, the LocalEventListener interface) in
revision 679750.

We can reintroduce the interface once we can leverage the extra information it gives to the
observation manager, but until that it's better to avoid having two different mechanisms for
the same functionality.

> Adding Event interface and isLocal()
> ------------------------------------
>                 Key: JCR-1672
>                 URL: https://issues.apache.org/jira/browse/JCR-1672
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-api, jackrabbit-core
>    Affects Versions: 1.4
>            Reporter: Carsten Ziegeler
>             Fix For: 1.5
>         Attachments: jackrabbit.patch, localeventlistener.patch
> when a repository cluster is used, it seems that a common problem many people have is
to detect if an observation event is send because of changes on the local instance or a remote
instance of the cluster.
> This is especially important if you want to do post processing of data
> based on observation (the post processing should only be done by one instance in the
> A current solution is to cast the jcr event object to the EventImpl of jackrabbit core
which is obviously not a nice solution :)
> So what about adding an event interface to jackrabbit api which extends the jcr event
interface and adds the isLocal() method? 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message