@Felix: Thanks for your fast reply. > Of course you can deploy the Sling Web Application in any context root you > like, the default of course being the root context. But what do I need to do that Sling "moves" requests coming from/through http://localhost:8080/sling/* down to http://localhost:8080/* ? Is this to be solved with mappings? I have setup the following mapping(s) /etc/map/ |-- [localhost_any]< sling:match = "localhost\.\d*" > |-- [sling]< sling:internalRedirect = "/" > to no avail...
Regards Clemens > -----Ursprüngliche Nachricht----- > Von: Felix Meschberger [mailto:[email protected]] > Gesendet: Donnerstag, 2. Dezember 2010 09:48 > An: [email protected] > Betreff: Re: What if sling is not deployed/run on the root '/' > > 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. > > 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 >
