On Fri, Apr 3, 2009 at 8:20 AM, Felix Meschberger <[email protected]> wrote:
> [...] > Do we want to keep the ResourceResolver.resolve(String path) method > return null if the reource cannot be found (backwards compatible case) > or do we want to have the method return NonExistingResource (consistency > case). If I can disregard the points of backwards compatibility and documentation for a second, I'd say: I've allways regarded NonExistingResource as something of a hack, so I wouldn't mind trying to avoid it as much as possible. A null returned when a resource does not exist, is certainly easier to grasp for Sling newbies. -- Vidar S. Ramdal <[email protected]> - http://www.idium.no Akersgata 16, N-0158 Oslo, Norway +47 21 531941, ext 2070
