You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2014/03/25 15:25:19 UTC
[jira] [Comment Edited] (OAK-1174) Inconsistent handling of invalid
names/paths
[ https://issues.apache.org/jira/browse/OAK-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946577#comment-13946577 ]
Michael Dürig edited comment on OAK-1174 at 3/25/14 2:25 PM:
-------------------------------------------------------------
Just from quickly looking at it, the patch looks good. Please also check for performance regressions. This part of the code is very sensitive to that respect.
[~jukkaz], could you also have a quick look at this?
PS: this was meant to got to OAK-1168.
was (Author: mduerig):
Just from quickly looking at it, the patch looks good. Please also check for performance regressions. This part of the code is very sensitive to that respect.
[~jukkaz], could you also have a quick look at this?
> Inconsistent handling of invalid names/paths
> --------------------------------------------
>
> Key: OAK-1174
> URL: https://issues.apache.org/jira/browse/OAK-1174
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: Michael Dürig
> Assignee: Jukka Zitting
> Priority: Minor
> Fix For: 0.20
>
>
> Passing an invalid name to a JCR method might or might not throw a {{RepositoryException}} depending on whether name re-mappings exist or not:
> {code}
> session.itemExists("/jcr:cont]ent");
> {code}
> returns {{false}} if no name re-mappings exist but throws a {{RepositoryException}} otherwise.
--
This message was sent by Atlassian JIRA
(v6.2#6252)