You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2016/11/25 13:13:58 UTC
[jira] [Commented] (SLING-6327)
ResourceResolverImpl.isResourceType() should compare relative resource
types (and ignore any search path prefixes)
[ https://issues.apache.org/jira/browse/SLING-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15695841#comment-15695841 ]
Robert Munteanu commented on SLING-6327:
----------------------------------------
Looks like there are more adjustments to be made - the launchpad build is now broken, apparently due to this change
https://builds.apache.org/job/sling-launchpad-builder-1.8/290/console
> ResourceResolverImpl.isResourceType() should compare relative resource types (and ignore any search path prefixes)
> ------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-6327
> URL: https://issues.apache.org/jira/browse/SLING-6327
> Project: Sling
> Issue Type: Improvement
> Components: ResourceResolver
> Affects Versions: API 2.15.0, Resource Resolver 1.5.2
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Fix For: API 2.15.2, Resource Resolver 1.5.6
>
> Attachments: SLING-6327-v01.patch
>
>
> Currently the following two expressions return false
> {{ResourceResolverImpl.isResourceType(<Resource with resourceType="sling/some/type">, "/libs/sling/some/type"}}
> {{ResourceResolverImpl.isResourceType(<Resource with resourceType="/libs/sling/some/type">, "sling/some/type"}}
> Since it cannot always be influenced whether the given resource is absolute or relative (because both usually works from a rendering perspective when you talk about the current request's resource), both cases should actually return {{true}}.
> See also the related discussion at http://www.mail-archive.com/dev@sling.apache.org/msg62351.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)