[
https://issues.apache.org/jira/browse/JCR-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12645220#action_12645220
]
alexander.klimetschek edited comment on JCR-1847 at 11/5/08 5:59 AM:
---------------------------------------------------------------------
Ok, that's why I noted to maybe use another specific exception. That one would
have to be created in spi then.
Or turn it around and not use the spi interfaces as utility methods in internal
code (such as the mentioned ObservationManagerImpl, where the Path interface is
used for parsing + checking path strings passed in the normal JCR API), but
create another Path utility interface for that.
was (Author: alexander.klimetschek):
Ok, that's why a noted to maybe use another specific exception. That one
would have to be created in spi then.
Or turn it around and not use the spi interfaces as utility methods in internal
code (such as the mentioned ObservationManagerImpl, where the Path interface is
used for parsing + checking path strings passed in the normal JCR API.
> Path methods should throw NameEx instead of RepositoryEx
> --------------------------------------------------------
>
> Key: JCR-1847
> URL: https://issues.apache.org/jira/browse/JCR-1847
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-spi
> Reporter: Alexander Klimetschek
> 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.
