Hi,
That's what I was wondering, is a nodeExists() call followed by
getNodes() better than a getNodes() call by itself? Especially if we
assume potential network overhead for both calls...
That pattern pops up all over again. We should probably not use
exceptions for signalling missing values but use null instead and use
exceptions for exceptional cases.
I agree. What about
(a) getNodes() can return null, like java.util.Map.get(), or
(b) getNodesOrNull() is added, and getNodes would still throw an exception.
I think the pattern "if nodeExists then getNodes" should be avoided also
because the node might have been deleted just after calling nodeExists,
depending on the underlying storage.
Regards,
Thomas
10 messages in org.apache.jackrabbit.oak-commitsRe: svn commit: r1309458 - /jackrabbi...