[
https://issues.apache.org/jira/browse/SLING-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13462555#comment-13462555
]
Antonio Sanso commented on SLING-2562:
--------------------------------------
good stuff Konrad,
The only issue as you mentioned is the use of two internal implementation from
the engine bundle.
Just taking a stab here giving a look to
org.apache.sling.engine.impl.request.SlingRequestPathInfo and
SlingRequestProgressTracker do not contain to much logic and internal
dependencies so they might easily become inner class of the
SimpleSlingHttpServletRequestWrapper.
WDYT?
> 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, SLING-2562-v1.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
