Currently the definitions from parsysConfigs of child and parent will be merged:
If you have an inheritance hierarchy of page components using sling:resourceSuperType you can define a wcmioarsysConfig on each level of this hierarchy. The definitions are merged together according to the inheritance hierarchy.
It would be nice to have the possibility to override the allowance definition of parent for certain path.
when you do not want to inherit anything from the super resource type, there might by better alternatives:
do not inherit from the super page component
choose a different name then "content" for the parsys, this also breaks the inheritance chain
thus i'm not sure if an approach with overrideSuperType:true makes sense.
I'd like to inherit everything from the super page component (all configs and html). The only difference is that the inherited page should allow the reduced list of children components in its content.
Your approach with deniedChildren would surely also solve the problem.
and the approach of just using a different name than "content" for the parsys where you do not want to inherit any child component definitions?
don't understand this approach cause I'd like to use the same sightly template from the super page component
i've implemented both approaches:
add deniedChildren parameter (which was aldready implemented for osgi configs, it's now available for settting in the resource type definition as well)
add inherited parameter. this is true by default, if you set it to false it cancels the inheritance from the super resource type