On 10/18/07, Felix Meschberger <[EMAIL PROTECTED]> wrote: > ... // return the main content of the current request > Content getContent(); > // return a content address by path > Content getContent(String path) throws SlingException; > // list the children of the named content > Enumeration<Content> getChildren(Content content) throws > SlingException; >...
Why do we need this in the general case? If the Resource is a JCR node, that gives full access to JCR navigation features, which cover the above and much more (or am I missing something?). If this is needed for OCM-mapped objects only, then IMHO that's an OCM concern, which might warrant a helper class, but does not deserve adding stuff to our (currently lean and mean) Resource interface. -Bertrand
