[
https://issues.apache.org/jira/browse/SLING-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193666#comment-13193666
]
Felix Meschberger commented on SLING-2385:
------------------------------------------
IIRC I have introduced this method to be called from the
ResourceResolver.resolve(HttpServletRequest, String) implementation.
The reason for having this method is to support special integrations like
JAX-RS (JSR-311, JSR-339) where the request object might be required to resolve
the appropriate JAX-RS servlet to back the Resource and ultimately handle the
request.
If this method is not called we should probably fix this in the
JcrResourceResolverImpl class.
> Deprecate or use ResourceProvider#getResource(ResourceResolver,
> HttpServletRequest, String)
> --------------------------------------------------------------------------------------------
>
> Key: SLING-2385
> URL: https://issues.apache.org/jira/browse/SLING-2385
> Project: Sling
> Issue Type: Task
> Components: API
> Affects Versions: API 2.2.2
> Reporter: Carsten Ziegeler
>
> The ResourceProvider interface contains currently this method:
> Resource getResource(ResourceResolver resourceResolver,
> HttpServletRequest request, String path);
> which is not used at all
> I think we should either use it in the implementation, or deprecate it
> Looking at how our resource resolution currently works, deprecating looks
> like the better option
--
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
