[
https://issues.apache.org/jira/browse/SLING-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653954#comment-14653954
]
Bertrand Delacretaz commented on SLING-3529:
--------------------------------------------
I also have a prototype with a slightly different mechanism at SLING-4851 - the
main difference is that it uses a more active model where components that want
the startup to wait between start levels register a {{StartLevelChangeBarrier}}
service [1] to signal that. This should allow us to get rid of the wait that we
have between start levels in the current startup handling, by letting
components (it's just the installer for now AFAIK) provide an optimal waiting
mechanism.
(using a counter in the barrier was not popular when we discussed that on
dl-dev, but changing to a single flag is easy)
[1]
https://svn.apache.org/repos/asf/sling/whiteboard/bdelacretaz/startup-stuff/startup-sequencer/src/main/java/org/apache/sling/startup/sequencer/StartLevelChangeBarrier.java
> Move startup handling to a separate bundle
> ------------------------------------------
>
> Key: SLING-3529
> URL: https://issues.apache.org/jira/browse/SLING-3529
> Project: Sling
> Issue Type: New Feature
> Components: Launchpad
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
>
> The startup handler is currently embedded in the Sling launchpad base - which
> makes it impossible to use when Sling is installed in another container like
> e.g. Apache Karaf.
> We should move this to a separate bundle to make it more reusable
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
