[
https://issues.apache.org/jira/browse/JCR-1328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560405#action_12560405
]
Felix Meschberger commented on JCR-1328:
----------------------------------------
> I'd actually prefer to modify all methods that take JCR paths to treat the
> referenced item as not found
If a MalformedPathException would be thrown, we could react accordingly. As
such it would be more helpful than just acting as if the item does not exists.
The correct behaviour probably depends on the concrete method.
> Session.itemExists implementation wrong
> ---------------------------------------
>
> Key: JCR-1328
> URL: https://issues.apache.org/jira/browse/JCR-1328
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.4
> Reporter: Felix Meschberger
>
> IMHO the implementation of the Session.itemExists(String) method is wrong
> when called with a malformed path such as "/a/b/c/*" (note the trailing
> star). According to the spec, the method must return "false" for a malformed
> path like this.
> In reality, the method throws a RepositoryException which is allowed to be
> thrown by the spec "if an error occurrs" (whatever that means). But catching
> this exception means, we cannot handle it: Is it a connection issue or a
> general repository problem ? If so, I cannot do anything about it. It is
> really a path problem, I can do something about it. But how do I know
> (without rebuilding internals) ?
> See also SLING-152 for more info.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
