Felix Meschberger wrote
> Hi,
>
> Sling is always registered as the root servlet of the web application.
> We cannot currently change this. The sling.root configuration property
> has in fact been removed, because it was not supported.
>
> Of course you can deploy the Sling Web Application in any context root
> you like, the default of course being the root context.
>
In addition, if you're deploying Sling as a web application, you can
mount the bridge servlet to any path within the web app context -
currently it is mounted at the root.
So if you mount your web app at context /foo, you can mount the bridge
servlet at /bar, therefore Sling responds to everything starting with
/foo/bar.
Regards
Carsten
> Am Donnerstag, den 02.12.2010, 09:12 +0100 schrieb Clemens Wyss:
>> What ist he easiest way to deploy/run sling not on root '/', but, for
>> example, beneath '/sling/'? Can this be "handled" by a simple sling:Mapping
>> (internalRedirect) node beneath /etc/map?
>> There used to be the sling.root Servlet property...(*)
>>
>> Thx for your advices
>> Clemens
>> (*)Btw, if I put sling.root into the sling servlet initParams it is written
>> into the sling.properties file
>
> Yes. Everything that's in the servlet's init-param is copied into the
> sling.properties file in ${sling.home}. As such ${sling.home} actually
> reflects the set of the current framework properties set by Sling.
>
> Regards
> Felix
>
>
>
--
Carsten Ziegeler
[email protected]
