> 2013/3/6 Mike Müller <[email protected]>: > >> Just to throw in some more ideas :) what about a decorator for > >> resource providers? This would also solve the use case of easily > >> adding additional checks to resource providers who don't have their > >> own access checks without needing to code this into each and every > >> provider. > >> > >> And a ResourceProviderDecorator would work for me much better than a > >> ResourceResolverDecorator :) > > > > A ResourceProviderDecorator couldn't do the job, because some operations > > are on the ResourceResolver at the moment (delete, create but also > > findResources > > and queryResources). > > All of them are on the provider: ModifyingResourceProvider and > QueriableResourceProvider. > > The resolver just deletages.
Yes, I have overseen that, Carsten is right. We could do it with a ResourceProviderDecorator. If we do that, we could implement a service param (or something else) in a way that's easy To only decorate some providers. So someone can decorate for example only providers without ACLs... Best regards mike
