[
https://issues.apache.org/jira/browse/SLING-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704028#action_12704028
]
Felix Meschberger commented on SLING-904:
-----------------------------------------
What requirements does the worker thread have ? What operations can the worker
thread not do if a service is not available ?
* ConfigurationAdmin: only required to apply configuration, if service is not
here, just delay applying configurations
* PackageAdmin: This service is always present or never present (at least in
the Felix framework)
* StartLevel: This service is always present or never present (at least in
the Felix framework)
I think the worker thread should be a separate component in a separate class,
which makes it much easier to maintain.
The problem is, that the JCRInstall bundle is suceptible to package dependency
changes. This may cause the bundle to be restarted and thus the state being
lost (unless there is some persistence). For this reason, a second bundle with
just the worker functionality would be much stabler since there are much less
dependencies.
> jcrinstall - take three
> -----------------------
>
> Key: SLING-904
> URL: https://issues.apache.org/jira/browse/SLING-904
> Project: Sling
> Issue Type: Improvement
> Components: JCR Install
> Reporter: Bertrand Delacretaz
>
> Refactor and reengineer jcrinstall based on the accumulated experiences of
> the "take two", SLING-646.
> See discussion in http://markmail.org/message/ld6tkz6fdseknntx
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
