[
https://issues.apache.org/jira/browse/SLING-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700807#action_12700807
]
Bertrand Delacretaz commented on SLING-904:
-------------------------------------------
Considering SLING-931, it might be useful to split jcrinstall in two (or three)
bundles:
1) OSGi controller bundle, no dependencies except framework and log bundles, so
that the bundle is "never" restarted during update operations. Maybe split in
two, with a "worker" bundle with minimal dependencies, depending on what
dependencies are needed in total.
This bundle has no dependencies to Sling or JCR, and can be used to install
from filesystems or other sources as well.
2) Repository observer bundle, watches the JCR repository and sends commands to
the OSGi controller bundle. This bundle restarts much more often, for example
when the SlingRepository service restarts.
> 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.
