You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2023/06/20 15:26:00 UTC
[jira] [Updated] (SLING-11911) Use proper resource resolving in Sling Servlet Resolver web console
[ https://issues.apache.org/jira/browse/SLING-11911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-11911:
------------------------------------
Fix Version/s: Servlets Resolver 2.9.14
> Use proper resource resolving in Sling Servlet Resolver web console
> -------------------------------------------------------------------
>
> Key: SLING-11911
> URL: https://issues.apache.org/jira/browse/SLING-11911
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Affects Versions: Servlets Resolver 2.9.12
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Servlets Resolver 2.9.14
>
>
> For historical reason the servlet resolver web console didn't actually resolve the resource to correctly decompose the URL but always used a heuristics. With SlingUriBuilder providing the method {{SlingUriBuilder.rebaseResourcePath()}} this now became much simpler and we can easily do the resolving in the web console in the same way like it is done in Sling.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)