[
https://issues.apache.org/jira/browse/SLING-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585730#action_12585730
]
fmeschbe edited comment on SLING-359 at 4/4/08 1:13 PM:
-----------------------------------------------------------------
Currently global docroot mapping* is not supported. So to support the docroot
mapping for sling.js an explicit configuration entry for the mapping
/system/docroot->/ is required. Of course we could add such a default mapping
to the ResourceResolver to provider sling.js under /sling.js.
WDYT ?
* global docroot mapping is mapping of all docroot locations in the resource
tree to the root URL without having to configure the respective mapping for
each every such location.
was (Author: fmeschbe):
Currently the docroot mapping is not directly supported unless you
explicitly configure the mapping /system/docroot->/. Of course we could add
such a default mapping to the ResourceResolver to provider sling.js under
/sling.js.
Are there other opinions ?
> sling/sling.js path hidden by Sling console
> -------------------------------------------
>
> Key: SLING-359
> URL: https://issues.apache.org/jira/browse/SLING-359
> Project: Sling
> Issue Type: Bug
> Reporter: Bertrand Delacretaz
> Priority: Minor
>
> See http://markmail.org/message/osjab4dn2yis4uhd, the consensus seems to be
> to address this resource /system/sling.js - the idea being that /system will
> be reserved for resources that are usually provided directly by Sling, and do
> not come from the repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
