You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2012/08/01 16:25:04 UTC
[jira] [Commented] (SLING-2385) Deprecate or use
ResourceProvider#getResource(ResourceResolver, HttpServletRequest, String)
[ https://issues.apache.org/jira/browse/SLING-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426658#comment-13426658 ]
Carsten Ziegeler commented on SLING-2385:
-----------------------------------------
For now I have deprecated it, if that's not the right solution we should fix that :)
> 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
> Fix For: API 2.2.6
>
>
> 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