[ https://issues.apache.org/jira/browse/SLING-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert resolved SLING-6035. ----------------------------------- Resolution: Fixed Completed: At revision: 1759348 > ResourceBuilder: Support absolute paths > --------------------------------------- > > Key: SLING-6035 > URL: https://issues.apache.org/jira/browse/SLING-6035 > Project: Sling > Issue Type: Improvement > Components: Extensions > Reporter: Stefan Seifert > Assignee: Stefan Seifert > Priority: Minor > Fix For: Resource Builder 1.0.0 > > > follow-up from discussion in > [SLING-5356|https://issues.apache.org/jira/browse/SLING-5356?focusedCommentId=15458657#comment-15458657] > A) why not supporting absolute paths for resource creation? > example 1: > {noformat} > resourceBuilder = > getService(ResourceBuilder.class).forResolver(resourceResolver); > resourceBuilder.resource("content/page1", "sling:config-ref", > "/conf/content/page1"); > {noformat} > it would be clearer/cleaner to just write /content/page1 to make sure this > resource starts at the root, and not at an perhaps unknown parent location. > currently it's completely forbidden to use absoulte paths. -- This message was sent by Atlassian JIRA (v6.3.4#6332)