My understanding of this is slightly different. 1. The url specifies the resource. 2. The extension defines which rendering engine handles this request 3. It's the extension that uses the information in the resource to determine the script/scripts to be executed, with the default html engine utilizing the sling:resourceType to determine the execution script
When discussing different views for a resource, the key thing is that a URL should define one view. If you want a resource to be displayed in different ways, you want to modify the URL to be different. Either by extension or selector. -- Jason On Mon, Jul 11, 2016, at 01:20 PM, vkum14 wrote: > I guess what Shivika is referring to as view is actually Script: > In sling request, first resource is resolved and sling:resourceType > property > in that node is using by ServletResolver to identify the best script in > the > folder on path of sling:resourceType property value. Which actually > results > into one to one mapping between a component and the folder which contains > the script. Is there a way where-in sling:resourceType can be an array in > defined sequence of folders to be used by ServletResolver to find the > script? Or any other idea might be ResourceMerger? > > Hope that helps! > > > > -- > View this message in context: > http://apache-sling.73963.n3.nabble.com/One-Resource-to-multiple-views-in-different-locations-tp4061093p4062395.html > Sent from the Sling - Users mailing list archive at Nabble.com.
