Hi, Thanks a lot for the insight, however I'm under the impression that the approaches suggested imply the creation of content nodes for each and every resource right ?
for example it's not possible to have something like /libs/acme/scripts/js1.js /libs/acme/scripts/component1/js11.js /libs/acme/scripts/component1/component11/js111.js without building components for each and every file. What I was thinking was some way to pick and choose between apps and libs without explicit content configuration for each and every node. In the past I've built a custom resource resolver to integrate another content server with Sling and I'm now wondering if same strategy could be used with minimal configuration, for instance to configure a node to have this overlay behavior for each and every child node by specifying only the root overlaying node or something like that. Regards, Ivo Leitão -- Sent from: http://apache-sling.73963.n3.nabble.com/Sling-Users-f73968.html
