commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16283] - Inproper use of Exception
Date Sat, 01 Feb 2003 20:29:24 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16283>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16283

Inproper use of Exception

treaves@silverfields.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |



------- Additional Comments From treaves@silverfields.com  2003-02-01 20:29 -------
Thanks for responding.

You make two arguments for not fixing this bug.  I'll respond to both.

a) as to breaking backwards compatibility, that is what the entire idea of
deprecation is about.  It was added to the Java semantic model to allow for this
very issue.  As to the major / minor version, perhaps it would have to wait, but
that in no way invalidates the issue.

b) as to offering a concrete  change, it was directly implied that every case
where a java.lang.Exception is thrown should be replaced with throwing an
exception that is appropriate for the error that occurred.  This is concrete,
although perhaps a bit open ended.

You also state that this was a matter of my opinion. This is not correct.  It is
a matter of fact.  Being a matter of fact does not of course imply that it is
correct.  But it is not a matter of opinion.  

I won't take the time to give you a lesson in OO language; I assume you're at
least somewhat familiar.  I will point out, however, that one of the tenets of
an OO language is the concept of sub-classing.  This allows reuse of code (the
Exception class in this case) while at the same time allowing for a more
specific instance of a class to be used to denote more concrete aspects of the
system (i.e. java.lang.ClassNotFoundException).  It is not a matter of opinion,
but a very basic concept of any OO system.

Perhaps this would be best handled as a feature request.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message