>>> [...] >>> As an alternative -- short term -- approach, you might want to implement >>> a ResourceProvider - say - for the /apps tree, which just uses >>> SlingRepository.loginAdministrative() to login to the default workspace >>> as an administrative user and which would serve the /apps tree from there. >> >> Hmm, hadn't thought of that solution. But when you say implement a >> ResourceProvider for /apps, would it be possible to implement a >> ResourceProvider for the "draft" workspace instead?
On Tue, Nov 11, 2008 at 3:49 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > Sure, the problem is then how to get the credentials into your > ResourceProvider. > > In addition you are faced with another issue with the current definition > of the ResourceProvider interface: This is currently global and does not > know the concept of users etc. To implement your use case, you might > want to go for a Facade Implementation, where the Facade is registered > and hands over the method call to a real instance, which might be thread > (or request) -bound to support per-user differences. >> In either case, what (in your opinion) would be the easiest approach >> to implement the ResourceProvider? Extending JcrResourceProvider, or >> creating one from scratch, or something completely different? > I would assume that starting from the existing JcrResourceProvider is > probably a good idea because this one already contains most of the core > code required. You just need some integration glue to get it running, > probably. > > Hope this helps Thanks a lot. I think we will hack up something for now, using a fake login to the draft workspace, and wait for ResourceResolverFactory :) -- Vidar S. Ramdal <[EMAIL PROTECTED]> - http://www.idium.no Akersgata 16, N-0158 Oslo, Norway
