Hey Vkmag,

I only showed you like two lines ;) of course the handling of this is a lot 
more than this. There is a check that they both inherit from the same 
/apps/site-common/components/header component, with a fallback to the 
site-common header component and stuff like that. You can all do that, thats up 
to you to figure out what requirements you have :D

Greetings,
Roy
> On 14 Jul 2016, at 11:09, vkum14 <vkuma...@sapient.com> wrote:
> 
> Yes but my use case demands to do the same with same component as to avoid 
> defining a new component when more brands come onboard. Have you done that 
> sort of something as well?
> 
> VINEET KUMAR
> Sr. Specialist
> -
> SapientNitro
> Gurgaon Infospace Limited SEZ, Ground Floor, Tower A, Building 2,
> Sector 21, Old Delhi-Gurgaon Road, Dundahera
> Gurgaon 122 016
> Haryana, India
> 
> desk  +91-124-676-7695
> mobile  +91-88-609-99936
> 
> The information transmitted is intended only for the person or entity to 
> which it is addressed and may contain confidential and/or privileged 
> material. Any review, retransmission, dissemination or other use of, or 
> taking of any action in reliance upon, this information by persons or 
> entities other than the intended recipient is prohibited. If you received 
> this in error, please contact the sender and delete the material from any 
> computer.
> 
> From: Roy Teeuwen [via Apache Sling] 
> [mailto:ml-node+s73963n4062546...@n3.nabble.com]
> Sent: Thursday, July 14, 2016 2:37 PM
> To: Vineet Kumar
> Subject: Re: One Resource to multiple views in different locations
> 
> Two components, as you can clearly see I said we have a component at 
> /apps/siteA/components/header and /apps/siteB/components/header
> 
>> On 14 Jul 2016, at 10:28, vkum14 <[hidden 
>> email]</user/SendEmail.jtp?type=node&node=4062546&i=0>> 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://apache-sling.73963.n3.nabble.com/One-Resource-to-multiple-views-in-different-locations-tp4061093p4062545.html
>> Sent from the Sling - Users mailing list archive at Nabble.com.
> 
> 
> ________________________________
> If you reply to this email, your message will be added to the discussion 
> below:
> http://apache-sling.73963.n3.nabble.com/One-Resource-to-multiple-views-in-different-locations-tp4061093p4062546.html
> To unsubscribe from One Resource to multiple views in different locations, 
> click 
> here<http://apache-sling.73963.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4061093&code=dmt1bWFyMTRAc2FwaWVudC5jb218NDA2MTA5M3wyNTc5NzAxODA=>.
> NAML<http://apache-sling.73963.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
> 
> 
> 
> 
> --
> View this message in context: 
> http://apache-sling.73963.n3.nabble.com/One-Resource-to-multiple-views-in-different-locations-tp4061093p4062548.html
> Sent from the Sling - Users mailing list archive at Nabble.com.

Reply via email to