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 2008/09/01 09:03:44 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=12627403#action_12627403 ]
Bertrand Delacretaz commented on SLING-490:
-------------------------------------------
As discussed in http://markmail.org/message/4qf7hc6vufzpcsnv it might be useful to allow the "readyness flag" to be reset, to cause the readyness to be evaluated from scratch again.
This would be useful in development: resetting the flag after a bundle update (assuming the OSGi console or whatever is doing the update generates an event when that happens) would cause Sling to return a 503 code until the update is complete.
> 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.
-
You can reply to this email to add a comment to the issue online.