[
https://issues.apache.org/jira/browse/SLING-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-2365.
--------------------------------------
Resolution: Fixed
Implemented this change in Rev. 1231167
I also moved the extraction of resource type information from the resource
underlying the event into the separate thread. This, as a side effect, enforces
single-threaded resource resolver use.
> JcrResourceListener: Asynchronously post Events to EventAdmin
> -------------------------------------------------------------
>
> Key: SLING-2365
> URL: https://issues.apache.org/jira/browse/SLING-2365
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.0.10
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.1.0
>
>
> Currently the JcrResourceListener posts events to the OSGi EventAdmin as it
> processes the JCR events.
> This may create a considerable delay on the repository observation queue
> processing because each call to the EventAdmin.postEvent must immediately
> extract the appropriate EventHandler services from the service registry.
> During JCR Event processing, we should only generate the OSGi events and post
> pone actual posting of events to a separate thread.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
