RE: One Resource to multiple views in different locations

/components/header > On 14 Jul 2016, at 10:28, vkum14 <[hidden > email]> wrote: > > Sounds good. One quick qns- did you have 2 components or one component since > you seem to be playing around with resourcetype? > > > > -- > View this message in context: > http

Re: One Resource to multiple views in different locations

Sounds good. One quick qns- did you have 2 components or one component since you seem to be playing around with resourcetype? -- View this message in context: http://apache-sling.73963.n3.nabble.com/One-Resource-to-multiple-views-in-different-locations-tp4061093p4062545.html Sent from the

Re: Use of request/resource wrappers

Or even simpler, let your application has a landing jsp which will have this business logic of adding selector using sling:include. We have used this and working properly. -- View this message in context:

RE: Configuration support for multi-tenant use cases

Thanks Carsten, so helpful. Could you please let me know the process (point me if this is documented somewhere) of contributing back to Sling? We might want to add this feature not in Sling core but only in Sling extensions. Thanks, VINEET KUMAR Sr. Specialist - SapientNitro Gurgaon Infospace

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

Re: Configuration support for multi-tenant use cases

Thanks Carsten for the response. We had thought about the same approach but calculating the configuration every time using this way did not seem good to us and we happened to define a config node (for example config.xyz) and then used configadmin to pick this up. This seems easier to manage also

Re: One Resource to multiple views in different locations

Thanks Jason for the response. I agree with you but my query was a little different. Please allow me to explain this in detail: *Scenarios:* 1. Consider following content structure /content/site/en/home [cq:page] - breadcrumb [sling:resourceType=site/components/breadcrumb] 2. Consider following

Re: One Resource to multiple views in different locations

Thanks Bertrand and I completely agree. Just posted detailed query around the same so please have a look and let me know if that makes sense. -- View this message in context: http://apache-sling.73963.n3.nabble.com/One-Resource-to-multiple-views-in-different-locations-tp4061093p4062450.html

Configuration support for multi-tenant use cases

All there, We are trying to host multiple tenants on the same sling instance and trying to figure out how we could have OOTB configuration support this model where-in a service is not just run-mode aware but tenant aware as well since one tenant could have different configurations than another.

Re: One Resource to multiple views in different locations

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