jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Klimetschek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1847) Path methods should throw a specific exception instead of RepositoryEx
Date Tue, 17 Feb 2009 19:55:00 GMT

    [ https://issues.apache.org/jira/browse/JCR-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674340#action_12674340

Alexander Klimetschek commented on JCR-1847:

> introducing "a helper class had its own exception" just restores the situation we had
with "BaseException" and which we finally got rid of.

AFAIK BaseException was used for everything in commons, so it has not the same semantics as
a (new) "InvalidPathException".

But the longer I look at it, the real issue is that internal code uses the spi Path interface
for path related utilites - which seems not right to me - especially if there is no specific
exception for a malformed path, what I would consider as a missing feature of that utility

> Path methods should throw a specific exception instead of RepositoryEx
> ----------------------------------------------------------------------
>                 Key: JCR-1847
>                 URL: https://issues.apache.org/jira/browse/JCR-1847
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-spi
>            Reporter: Alexander Klimetschek
>            Assignee: angela
>            Priority: Minor
> The o.a.j.spi.Path interface declares most methods to throw a RepositoryEx, whereas a
o.a.j.spi.commons.conversion.NameEx (or another specific exception) would make more sense,
since the RepositoryEx is too generic for what seems to be a "malformed names/path" nature
for all things that happen in a Path implementation.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message