You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/01/18 15:36:33 UTC
[jira] Updated: (JCR-1328) Session.itemExists implementation wrong
[ https://issues.apache.org/jira/browse/JCR-1328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated JCR-1328:
-----------------------------------
Attachment: JCR-1328.patch
Proposed patch
> 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
> Attachments: JCR-1328.patch
>
>
> 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.