[
https://issues.apache.org/jira/browse/SLING-12815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-12815.
-------------------------------------
Resolution: Fixed
Fixed in
https://github.com/apache/sling-org-apache-sling-api/commit/5767e54f23e043bce2b2d3785b467b053d06dda4.
> Expose methods to escape/unescape characters which are invalid in Sling
> Resource names
> --------------------------------------------------------------------------------------
>
> Key: SLING-12815
> URL: https://issues.apache.org/jira/browse/SLING-12815
> Project: Sling
> Issue Type: Improvement
> Components: API
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: API 3.0.0
>
>
> Sling API imposes the following restrictions for resource names:
> # No slash must be used (as used as path separator characters)
> # No names only consisting of dots must be used (as used as relative path
> specifiers in {{ResourceResolver.getResource()}}.
> Although most resource providers impose additional restrictions there should
> be some default escape/unescape mechanism which can be used to escape those
> characters. This is always useful together with {{SyntheticResources}} which
> live outside the resource resolver reign.
> Compare with the discussion at
> https://lists.apache.org/thread/cbpksrfm30jy070qxxq02qwxrb8l0v2s
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
