> On Thu, Nov 14, 2013 at 2:35 PM, Felix Meschberger > <[email protected]>wrote: > > > Hi > > > > Sure you can do it, but it (a) doesn’t match the idea of an access gate > > (at least not in my little brain cells) and (b) it is not comprehensive > > since the JCR Resource Provider does not leverage that. (b) is IMHO the one > > reason breaking the idea. > > > > Although I disagree on a (what else is this but restriction of access > (don't mix it with permission by default) if b is the case (so it could not > be granted to act on the global resource Tree I agree this would be a no go >
The ResourceAccessGate could be used for every resource provider, it's only not configured for JCRResourceProvider (but could by just setting a flag in the OSGi configuration). The good reason for not enabling it is that ACLs of the JCR shouldn't be mixed up with custom ACLs. But in the use case of enabling features or not, ResourceAccessGate could be a lean solution to hide some resources and does not mix up with ACLs. best regards mike
