[
https://issues.apache.org/jira/browse/JCR-1328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated JCR-1328:
-------------------------------
Priority: Minor (was: Major)
Affects Version/s: (was: 1.4)
Issue Type: Improvement (was: Bug)
I turned this into an improvement request as there seems to be consensus that
throwing an exception is the correct behaviour even though JSR 170 specifies a
false return value for malformed paths.
The improvement would be to throw something more specific than
RepositoryException.
> Session.itemExists implementation wrong
> ---------------------------------------
>
> Key: JCR-1328
> URL: https://issues.apache.org/jira/browse/JCR-1328
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Felix Meschberger
> Priority: Minor
> 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.
