Ian Boston wrote: > I am after is a listener that only fires on the cluster node that > created it. I need this because I want to ensure that all nodes, however > they are created have certain properties (like the id of the creator) if > appropriate. > > The only way I have found to do this is a SynchronousEventListener, > however this is internal to Jackrabbit and so its not possible to > activate a bundle containing this. > > The SLING-944 patch starts to get close, but its bound to EventListener > so one copy of the event will fire on all nodes in a cluster, depending > on how the OSGi Event admin service is wired this might mean that you > will see duplicates of the event in a cluster..... so your use case may > be the same. Ah good point - yes, I forgot about this one :) The Sling Event bundle is something we built on top of the OSGi eventing. It distributes OSGi events across a cluster. Now for the JCR Eventing to OSGi events bridge we will make use of this: jcr events are not distributed by the sling eventing mechanism - as the jcr cluster already distributes these events. However we will "mark" these events correctly (using the interface Alex mentioned in the other mail) and you can then use the EventUtil class from the sling event bundle to detect if the event is a local one.
I'll start on this stuff right after the release :) Carsten -- Carsten Ziegeler cziege...@apache.org
