On Thu, May 29, 2008 at 12:49 PM, Erik Buene <[EMAIL PROTECTED]> wrote: > However our application requires some processing of events when nodes in the > repository changes - this processing will in turn perform other changes in > the repository. This should just be done by one node (the "local" node that > triggered the event).
You could run the event listener only on one node. To make a distinction between the two instances, you could store some information in the repository, so that only one node is actually processing the data (something like event already handled). This way you have the same event listeners on both nodes, but only react on the events on one node. > Sadly, the jcr Event interface does not have any method to determine if an > event is local or external - but it seems the Jackrabbit implementation > (org.apache.jackrabbit.core.observation.EventImpl) does. You should avoid this. EventImpl might change and OSGi makes a clear distinction between public API and implementation - it simply blocks access completely. This might be inconvenient in some situations but it makes the system future proof. Alex -- Alexander Klimetschek [EMAIL PROTECTED]
