[ https://issues.apache.org/jira/browse/SLING-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706451#action_12706451 ]
Carsten Ziegeler commented on SLING-957: ---------------------------------------- I haven't locked at the patch yet, but nevertheless I'm in favour of a more generic/Sling like solution, taking the resource tree into account. Something along the lines of https://issues.apache.org/jira/browse/SLING-944 > JCR EventListeners are not easy to create or write > -------------------------------------------------- > > Key: SLING-957 > URL: https://issues.apache.org/jira/browse/SLING-957 > Project: Sling > Issue Type: New Feature > Components: JCR > Reporter: Ian Boston > Attachments: RegisterableEventManager.patch > > > JCE EventListeners have some drawbacks in the current sling environment. > Its relatively expensive to register them as each provider needs its own jcr > session. > Its not possible to register synchronous event listeners as this is part of > the jackrabbit-server bundle. > The patch to follow adds an EventManager to jackrabbit-server that > ServiceTrack(s) a provider interface, registering InjectableEventListners as > normal jcr event listeners or sync event listeners. > This patch assumes that you trust all the code in the JVM and are happy > giving bundles access to the JCR System Session. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.