On Feb 13, 2008 9:25 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...Undisputed is the fact, that the Resource should have a link to the > ResourceResolver and not to the ResourceProvider.... Agreed, from a scripting point of view I think it's perfectly acceptable to have resource.resolver.listChildren() instead of the resource.listChildren that I introduced last week. It's a good thing to make people aware of the ResourceResolver. > ...Remains the question of whether we actually should provide additional > public methods and properties on an interface in a single scripting > language which is not available in any other context.... I agree that we should not do this, i.e. resource.resolver should map to a java Resource.getResourceResolver() method, so that all scripting environments use the same underlying object model. -Bertrand
