I know I am talking out of AEM experience, but I don’t see why one would only go for a flat resourceSuperType list?
The most simple example here where that would have massive consequences is in how you would build a page. At this moment you have a basepage, and X child pages which all have the basepage as resouceSuperType, inheriting everything from header to footer. Why would you ever want to break this ideal setup? Greetings Roy > On 19 Mar 2016, at 11:41, Carsten Ziegeler <[email protected]> wrote: > > Maybe we should tackle this in steps. From what I heard so far, it seems > we can agree on: > > a) forget about Resource#getResourceSuperType. This method is ignored > from now on (and deprecated) > > How about having a dedicated service, like: > > d) we create a service which has three methods > > // get the super type > String getResourceSuperType(ResourceResolver resolver, String > resourceType); > > // get an ordered list of all super types > List<String> getResourceSuperTypes(ResourceResolver resolver, String > resourceType) > > // check if resourceType is checkResourceType (either directly or one > of the parents > boolean isResourceType(ResourceResolver resolver, String resourceType, > String checkResourceType) > > Regards > Carsten > -- > Carsten Ziegeler > Adobe Research Switzerland > [email protected]
