You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2007/04/12 09:17:32 UTC

[jira] Updated: (JCR-691) Let NameException extend RepositoryException

     [ https://issues.apache.org/jira/browse/JCR-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-691:
------------------------------

    Fix Version/s:     (was: 1.3)

Dropping this from the 1.3 release to avoid unexpected issues.

> Let NameException extend RepositoryException
> --------------------------------------------
>
>                 Key: JCR-691
>                 URL: https://issues.apache.org/jira/browse/JCR-691
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: core
>            Reporter: Jukka Zitting
>            Priority: Minor
>         Attachments: NameException.patch
>
>
> Since the NameExceptions (IllegalNameException, UnknownPrefixException, etc.) are typically thrown when parsing or formatting JCR names at the JCR API level, it would make sense for the NameException class to extend RepositoryException instead of the internal BaseException. This idea is supported by the fact that the majority of cases where NameExceptions are encountered simply rethrow the exceptions wrapped inside RepositoryException instances. Making NameException extend RepositoryException would reduce the amount of try-catch blocks and wrapped exceptions.

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