On Fri, Apr 3, 2009 at 1:34 PM, Vidar Ramdal <[email protected]> wrote: > 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.
Yes, but that's why there are the "getResource()" methods (returning null) and the "advanced" resolve() methods that do all kind of fancy stuff (synthetic resources, virtual path mappings, etc.), which is required for request processing and other cases. It would only be consistent if all resolve methods would return nonexistent and all getResource would return null. Regards, Alex -- Alexander Klimetschek [email protected]
