Hi, Bertrand Delacretaz schrieb: > Hi, > > On Tue, Jun 9, 2009 at 8:03 AM, Felix Meschberger<fmesc...@gmail.com> wrote: >> Claude Vedovini schrieb: >>> ...I guess that now that each deployed sling servlet has it's own >>> subfolder under sling.home to store configuration to, then may be >>> overriding the sling.home from the system properties could be a good >>> idea. >> Since system properties apply to the whole VM, multiple sling web >> applications deployed to the same servlet container would then use the >> same sling.home system property, which will not work.... > > But if each deployed Sling servlet adds its own suffix (its context > path) to the base sling.home path, that would work, not? > > The best might be to allow overriding sling.home from system > properties (to allow people to control where that goes), yet have each > sling servlet add its own context path to that value to define its own > storage path.
I was also thinking about such a prefix. But I would then name it sling.home.prefix or such to not confuse the use of sling.home as the actual location or just the prefix. Just using this special prefix property as from the system properties looks ok for me. Regards Felix
