[
https://issues.apache.org/jira/browse/JCR-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537006
]
angela commented on JCR-691:
----------------------------
this issues has been addressed by JCR-1169: The NameException placed in the
spi-commons
which replaces the former o.a.j.name.NameException in jcr-commons extends from
RepositoryException. I guess we can mark i fixed for 1.4.
> Let NameException extend RepositoryException
> --------------------------------------------
>
> Key: JCR-691
> URL: https://issues.apache.org/jira/browse/JCR-691
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Jukka Zitting
> Priority: Minor
> Fix For: 1.4
>
> 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.
