Hi Alex, this is one way but just solves this partially since you completely rely on inclusions to happen, but sometimes you just walk the tree and collect the information of resources e.g. to draw the navigation - and for such situations it would then be required to add such logic to the rendering Code where you could just filter the ResourceTree beforehand.
Best regards, Dominik On Thu, Nov 14, 2013 at 10:48 PM, Alexander Klimetschek <aklim...@adobe.com>wrote: > On 14.11.2013, at 05:11, Dominik Süß <dominik.su...@gmail.com> wrote: > > > As mentioned earlier the majority of features I have implemented yet do > > have a frontendpart that would get rendered and it would add additional > > complexity if I have to use custom resourceTypes (inherited ones through > > superType) just to disable them based on such rules. > > Wouldn't you just filter those requests out on a high level, e.g. using a > servlet filter? Which can already be provided in a modular fashion by an > optional featureflags module. > > > Cheers, > Alex
