[
https://issues.apache.org/jira/browse/OAK-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556311#comment-13556311
]
Jukka Zitting commented on OAK-563:
-----------------------------------
The reason for using {{getOakPathOrThrowNotFound()}} in many cases is handling
of code like the following:
{code}
try {
node.getNode("{http://some.unknown.namespace.url/}name";);
} catch (PathNotFoundException e) {
// should end up in here
}
{code}
If we changed the logic to throw a generic {{RepositoryException}} in such a
case, there would be no easy way for the client to distinguish between the node
not being there and some internal repository problem making the node
inaccessible.
> Rename SessionDelegate...OrThrow methods
> ----------------------------------------
>
> Key: OAK-563
> URL: https://issues.apache.org/jira/browse/OAK-563
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Fix For: 0.6
>
> Attachments: OAK-563.patch
>
>
> As a fallout of OAK-553 there are some inconsistency in method naming in
> {{SessionDelegate}} now. We should align the names of the ...OrThrow methods.
> That is, drop the OrThrow suffixes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
