You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2012/11/27 14:13:58 UTC
[jira] [Commented] (SLING-490) SlingStatusServlet - find out
whether a Sling application is ready after startup
[ https://issues.apache.org/jira/browse/SLING-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504596#comment-13504596 ]
Bertrand Delacretaz commented on SLING-490:
-------------------------------------------
Revisiting that once again - we're much further down this road with the startup listener for example, so IMO we could now solve this cleanly, including the following requirements:
a) Provide a simple way to find out, from an OSGi component, when the Sling instance is ready - startup listener is probably good here
b) Provide http access to that information, for example via a /system/ready.txt URL that does not require login
c) Provide a simple way to hook tasks into the startup sequence, so that they run at configurable start levels.
For example "start threads A and B once start level reaches 12, and wait for them to exit before allowing the system to go higher than start level 12"
d) Document and test those mechanisms so that Sling users can use them for their own initialization or upgrade code
> SlingStatusServlet - find out whether a Sling application is ready after startup
> --------------------------------------------------------------------------------
>
> Key: SLING-490
> URL: https://issues.apache.org/jira/browse/SLING-490
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> Being discussed in http://markmail.org/message/jtdnqneoudxbmb6k
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira