[
https://issues.apache.org/jira/browse/SLING-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-564.
------------------------------------
Resolution: Won't Fix
> Improve Sling's RequestDispatcher implementation
> ------------------------------------------------
>
> Key: SLING-564
> URL: https://issues.apache.org/jira/browse/SLING-564
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Affects Versions: Engine 2.0.2
> Reporter: Felix Meschberger
> Priority: Major
>
> Currently Sling uses its own RequestDispatcher implementation and never gets
> back to the Servlet Container's request dispatcher. As such the dispatcher
> has some drawbacks:
> * Only resource paths are supported not "fully" URLs
> * Selectors, Extensions and query parameters are not supported in the path
> to acquire the dispatcher
> * RequestDispatcher.forward() is not implemented at all
> The Sling Request Dispatcher should be enanced to support for URLs outside
> the resource tree by delegating the servlet container's dispatcher. In
> addition selectors, extensions and query parameters should be supported.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
