Hi, Am Donnerstag, den 18.10.2007, 17:12 +0200 schrieb Bertrand Delacretaz: > I might agree about the relative resources, but why the children? And > why just the children axis and not the full > ancestors/descendants/siblings/next/previous axes?
Generally, there are two use cases: Access a resource and list the (direct) children. Hence the two methods getResource(Resource, String) and listChildren(Resource). > If navigation between Resources is needed and that cannot be covered > by JCR, I'd suggest making that a separate ResourceHierarchyNavigation > interface. This smells like "interface-itis" - another method, another interface :-) No I think, if we just ammend the existing interface, we would probably be fine. I agree, that we should keep the Resource lean and clean and hence these methods belong to the ResourceResolver. Regards Felix
