I think using a thread local is an implementation detail and TenantAware has a single method like
TenantResolver getTenantResolver() while TenantResolver has a single method Tenant getCurrentTenant() (Don't quote me on the names, its just the first option which came to my mind) And then either Tenant gets a method returning the additional search path, or we use a convention, like /libs/{tenantId} and /apps/{tenantId} The implementation of the tenant resolver would use a thread local Carsten 2014-02-25 19:18 GMT+01:00 Andreas Schaefer Sr. <schaef...@me.com>: > Ok, will adjust the wiki page. > > - Andy > > On Feb 25, 2014, at 1:11 AM, Bertrand Delacretaz <bdelacre...@apache.org> > wrote: > > > On Tue, Feb 25, 2014 at 2:41 AM, Andreas Schaefer Sr. <schaef...@me.com> > wrote: > >> ...it might a good idea to add the getSearchPathExtension() to the > Tenant... > > > > Shouldn't that rather be called getAdditionalSearchPaths? > > > > In Sling, "extension" means the .html at the end of a URL, IMO we > > should avoid reusing that term for other things, as much as possible. > > > > -Bertrand > > -- Carsten Ziegeler cziege...@apache.org