Hi Stefan/Julian, I did not yet have time to have a look at the detailed concepts of your implementation, but I agree there might be some overlap. I definitely have to check the presentation you did at adaptTo()
The way SLING-2986 works, is that the Resource provider leverages a ResourceMerger service, which contains the logic to merge resources. The idea is also to extend this service to work with sling:resourceSuperType later for instance. I'm happy to provide you some details if needed. Regards, Gilles 2013/10/11 Stefan Seifert <[email protected]> > >On Fri, Sep 27, 2013 at 11:59 AM, Carsten Ziegeler > ><[email protected]> wrote: > >> ...Not quite the same - but we might be able to share code / > >functionality... > > > >Yeah that's my main concern: the merging/overriding logic should use > >the same code. > > > >-Bertrand > > yes, i think this is a good thought as well. > i will start playing with this idea in context of > https://issues.apache.org/jira/browse/SLING-1778 in a separate github > repository and check if it is "feels good" or not. > currently i'm unsure where such a "shared piece of merging code" should be > placed within sling, but this can be decided later. > > stefan > >
