[
https://issues.apache.org/jira/browse/SLING-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-2562:
-----------------------------------
Attachment: servletresolverplugin.png
This screenshot shows an implementation of this feature. I can provide a patch,
but since the Servlet Resolver Interface doesn't provide a good API method for
that, I had to rely on the two internal implementations
org.apache.sling.engine.impl.request.SlingRequestPathInfo and
SlingRequestProgressTracker. If that's acceptable tell me, and I will try to
attach a patch.
Even better would be an additional method in the Sling Servlet Resolver
interface like
Servlet SlingServletResolver.resolveServlet(String url, String method /*POST or
GET*/)
> 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
