[jira] [Resolved] (SLING-1051) SLING_ROOT should be configurable

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-1051.
-------------------------------------
    Resolution: Won't Fix

With SLING-5782 we're now registering Sling using the http whiteboard. By defining a new mount path for the servlet context used by Sling, Sling can be moved to any path

> SLING_ROOT should be configurable
> ---------------------------------
>
>                 Key: SLING-1051
>                 URL: https://issues.apache.org/jira/browse/SLING-1051
>             Project: Sling
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: Engine 2.0.6
>            Reporter: Andreas Kollegger
>            Priority: Minor
>
> Currently, SLING_ROOT is hard-wired to always be root. This is convenient as a default deployment for Sling, but prevents Sling from being deployed to an OSGi container where it shares space with another web application. 
>     /**
>      * The registration path for the SlingMainServlet is hard wired to always
>      * be the root, aka "<code>/</code>" (value is "/").
>      */
>     private static final String SLING_ROOT = "/";
> This should be changed to allow the registration path to be configurable. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)