[
https://issues.apache.org/jira/browse/SLING-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2406.
-------------------------------------
Resolution: Fixed
With revision 1242130 the events are now sent as soon as possible. In addition,
sending has been moved to the listener which takes care of sending duplicate
events.
> Installer start event should already be sent when resources are provisioned
> ---------------------------------------------------------------------------
>
> Key: SLING-2406
> URL: https://issues.apache.org/jira/browse/SLING-2406
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Affects Versions: Installer Core 3.3.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Installer Core 3.3.6
>
>
> Currently the installer reports started/suspended events from the run loop.
> When new resources arrive from a provider, the preparation of those might
> take some time (like copying them to the file system etc.) in this case, the
> started event is reported way later than the resources are provided. It would
> make more sense to report the started event right when new resources arrive
> or resources are removed
--
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
