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

2007-04-12 Thread Jukka Zitting (JIRA) 

 [ 
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.

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

2006-12-27 Thread Jukka Zitting (JIRA) 
 [ http://issues.apache.org/jira/browse/JCR-691?page=all ]

Jukka Zitting updated JCR-691:
--

Attachment: NameException.patch

Attached NameException.patch (against trunk) that implements the proposed 
change and adjusts the code in jackrabbit-core accordingly.

 Let NameException extend RepositoryException
 

 Key: JCR-691
 URL: http://issues.apache.org/jira/browse/JCR-691
 Project: Jackrabbit
  Issue Type: Improvement
  Components: core
Reporter: Jukka Zitting
Priority: Minor
 Fix For: 1.3

 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.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira