[
https://issues.apache.org/jira/browse/SLING-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435963#comment-13435963
]
Felix Meschberger commented on SLING-2562:
------------------------------------------
Excellent idea ! I for myself would welcome such a patch.
And yes, it would require access to internals. So the plugin would probably
live as part of the Servlet Resolver implementation and as such is perfectly
able to use internal API -- It may even be created and registered from the
SlingServletResolver activator method to have such internal access.
Another extension would be to not only list the selected script, but also the
list of script candidates.
> Add a test for servlet resolver as Web Console Tab
> --------------------------------------------------
>
> Key: SLING-2562
> URL: https://issues.apache.org/jira/browse/SLING-2562
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Reporter: Konrad Windszus
> Attachments: servletresolverplugin.png
>
>
> Sometimes it is hard to tell which script/servlet answered a specific
> request. Therefore a tab which provides a test similar to "Configuration
> Test" in the "Sling Resource Resolver" Tab of the Felix Web Console would be
> very useful, which would provide the information which script/servlet was
> used for rendering a response.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
