Hi I have the impression this sounds like having „configurable“ (or dynamic) search paths on the ResourceResolver ?
Currently the search path is fixed at a configuration value. It might be conceivable that we make this more dynamically configurable. Regards Felix — Felix Meschberger | Principal Scientist | Adobe Am 31.10.2013 um 15:28 schrieb Alessandro Bologna <[email protected]>: > Hi, > I am pretty sure that the answer is simple enough, but somehow I couldn't > find it in the documentation. > Say that I have a resource /content/shared/foo with sling:resourceType > myapp/page, which will cause a request to invoke scripts at > /apps/myapp/page. > > For requests that have a specific header, say "Host:otherapp", I want > instead to use scripts located at /apps/myotherapp/page. > > Short of duplicating the resource, what's the best practice to implement > this? It doesn't seem that the mapping at[1] would help be because in the > end I need to change the base path of the resourceType... > > Thanks > Alessandro > > [1] > https://cwiki.apache.org/confluence/display/SLING/Flexible+Resource+Resolution
