I'm beginning to think that there is two different mental models that people who work with Sling take on. One is an OSGi model, where a solution can be achieved via a Service and the creation and configuration of that service(s). The other is a resource centric model where everything must be exposed as a resource, and be configurable by changing properties on a resource.
>From a resource pov the ResourceAccessGate is difficult and potentially fails >because I can't go through the resource tree and see what is and isn't >protected on the tree itself, nor can I configure a ResourcAccessGate by >defining permissions on a node. -- Jason On Thu, Oct 4, 2018, at 11:15 AM, Carsten Ziegeler wrote: > Why is that? I think that's a bold statement. > > ResourceAccessGate has been developed (afaik) with this use case in mind. > > Carsten > > > Bertrand Delacretaz wrote > > Hi, > > > > On Thu, Oct 4, 2018 at 4:43 PM Julian Sedding <[email protected]> wrote: > >> ...I am still convinced that this issue could be simply and > >> elegantly be solved with a ResourceAccessGate for both servlets and > >> scripts in a generic way... > > > > This would probably work but I think it's not intuitive at all, and as > > such error-prone. > > > > -Bertrand > > > -- > Carsten Ziegeler > Adobe Research Switzerland > [email protected]
