Resolution: Won't Fix
Affects Version/s: None
Fix Version/s: None
i remember that this has been discussed before but didn't manage to find
the corresponding issue.
while in theory the distinction between PathNotFoundException and ItemNotFoundException makes sense, i have
the impression that it turns out to be quite artificial in reality. while working on the remoting of JCR
calls over http it even turned out to be impossible to distinguish them, which lead to pretty ugly code
in the JCR implementation: catching PathNotFoundException and rethrowing it as ItemNotFoundException (or vice
versa) just because of the mere fact that the JCR API mandated the other exception.
would it be feasible to merge the two exceptions? or make either of them a subclass of the other?