[
https://issues.apache.org/jira/browse/SLING-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-145.
-----------------------------------
Resolution: Fixed
This issue has been solved in Rev. 615211 by merging the resource integration
into trunk as part of SLING-197. Therefore I close this issue.
> Apply same logic to servlet resolution as is used for script resolution
> -----------------------------------------------------------------------
>
> Key: SLING-145
> URL: https://issues.apache.org/jira/browse/SLING-145
> Project: Sling
> Issue Type: Improvement
> Components: ServletResolver
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> Currently servlets are resolved just by the resource type. On the other hand
> scripts are resolved based on the resource type, the request method, the
> request URI selectors and (for GET requests) the request URI extension.
> To be able to have more finegrained control on which servlet is used for
> which request, we should apply the same logics to the servlet resolution.
> This would also allow for providing GET handling servlets for certain
> resources while leaving resource content update to the default servlet.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
