Hi, On Sun, Nov 9, 2008 at 7:11 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > My proposal is to add a first-class Sling service interface called > ResourceResolverFactory which allows you to get a ResourceResolver > instances in one single shot.
The proposed ResourceResolverFactory looks pretty much like javax.jcr.Repository. The proposed credentials map defaults look like javax.jcr.SimpleCredentials and the workspaceName argument to Repository.login(). (BTW, what have things like workspace and session "hints" to do with credentials?) The proposed ResourceResolver.close() method is like Session.logout(). I find it troubling that Sling is reinventing JCR. This looks like a symptom that JCR is not optimal for the things Sling wants to do. From an architectural perspective I'd rather focus on improving JCR than layering extra levels of abstraction on top of it. BR, Jukka Zitting
