Hi, I think we have to separate between the JCR implementation, Jackrabbit, and Sling. Whatever Jackrabbit does/should do/should not do, is something for the Jackrabbit list. Of course, we can discuss suggestions for Jackrabbit on this list, so there is nothing wrong with the discussion here so far.
Now, Sling is based on the resource api - some people like it, some people don't - but that's the way how Sling works. The resource api already allows to access different content storages (like jcr, bundles, file system etc.) So, as we already have this flexibility in the api and Sling itself, it makes sense to remove the short-commings in some areas of our api. And the stuff proposed by Felix is exactly one of the main areas atm - if you build applications on Sling's api you'll soon hit this limitation. I didn't have time to read the proposal yet, so more comments soon. Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
