[jira] Closed: (SLING-733) Process resource detection and installation in sequence instead of asynchronously

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz closed SLING-733.
-------------------------------------

    Resolution: Fixed

Closing this issue for now, manual testing (adding and removing about 50 bundles repeatedly) looks good, we'll test more extensively in SLING-734

> Process resource detection and installation in sequence instead of asynchronously
> ---------------------------------------------------------------------------------
>
>                 Key: SLING-733
>                 URL: https://issues.apache.org/jira/browse/SLING-733
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR Install
>            Reporter: Bertrand Delacretaz
>
> Currently the RepositoryObserver's resource detection loop and the OsgiController's installation/update/delete loop run in their own separate threads.
> Running the detection and installation operations in sequence would make debugging and testing easier, and there are no downsides except maybe slightly slower processing of installed bundles and configs - I think the tradeoff is worth it, and it's simple to implement: I'll add a executeScheduledOperations() method to the OsgiController interface, which will be called by the RepositoryObserver at the end of its repository observation loop.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.