[
https://issues.apache.org/jira/browse/SLING-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12719166#action_12719166
]
Felix Meschberger commented on SLING-490:
-----------------------------------------
> It's no big deal to have to add the systemstatus bundle to existing setups,
> and the error message ("No SystemStatus service available") is clear enough
> to indicate the problem.
The message "No SystemStatus service available" is IMHO not very clear to the
casual end user: "what is the SystemStatus service for any way ?" ... A better
message would probably be something like "Unable to handle requests. System
status is unknown due to missing SystemStatus service."
> The idea is that /system/sling/status returns a plain text page with details
> about the current
> status, as reported by the status scripts found under /system/sling/status in
> the repository.
Hmm, the "status scripts" may not be available for execution if they depend on
any scripting language not yet available.
> This info could also be made available in a console plugin, is that what you
> mean?
That's what I mean.
The problem with the special treatment of the path is that (1) it is special
treatment (which I disgust from the bottom of my heart) and (2) it triggers the
doGet method no matter what HTTP request method has been used.
> 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.
