[
https://issues.apache.org/jira/browse/SLING-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Boston resolved SLING-957.
------------------------------
Resolution: Invalid
The patch is invalid because AFAICT its not possible for the EventManager to
access the RepositoryImpl which is required to get hold of a SystemSession.
The SystemSession could be faked up, but thats probably a bad idea, and the
repository that is injected is a SlingRepository so its possible to bind to
other repository implementations.
> 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.
