I've never needed to have the resource resolver select a different script. Referencing your example of breadcrumb. I've had the main breadcrumb script import the specific implementation based on a configuration.
/apps/www/components/breadcrumb/breadcrumb.jsp /apps/www/components/breadcrumb/breadcrumb-site1.jsp /apps/www/components/breadcrumb/breadcrumb-site2.jsp The main breadcrumb.jsp is always executed and within that script is the logic that determines which version of the breadcrumb we want to provide. At that point we pull in the relevant jsp to render the site specific markup. This keeps all your breadcrumb logic within a single structure. It also adds value in the form of being able to offer sites options on how they would like their breadcrumbs to look that could be controlled by configuration. -----Original Message----- From: vkum14 [mailto:vkuma...@sapient.com] Sent: Wednesday, July 13, 2016 10:27 AM To: users@sling.apache.org Subject: Re: One Resource to multiple views in different locations Hi Jason, I believe you are talking about css/js here while my use case is to have even different markups for the same component based on the site, it is being rendered. IMO, this is a typical use case of telling servletresourceresolver to pick different scripts based on the site input. Have you done some sorts of that? -- View this message in context: http://apache-sling.73963.n3.nabble.com/One-Resource-to-multiple-views-in-different-locations-tp4061093p4062511.html Sent from the Sling - Users mailing list archive at Nabble.com.
