hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38520] - charset error handling not compatible with Java 1.4
Date Mon, 06 Feb 2006 09:39:04 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38520>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38520





------- Additional Comments From http-async@dubioso.net  2006-02-06 10:39 -------
Hi Oleg,

two of the three JDKs I've tested with will throw an UnsupportedCharsetException
*although* the error is actually an IllegalCharsetNameException. Since different
JVMs do throw different exceptions for the *same* problem, I don't think it is a
good idea to handle these different exceptions differently in our code.

I don't see the point of implementing a fallback handling if you're not going
to fall back to it consistently. The fallback should apply in a specific
error situation, even if that situation is indicated by different exceptions
in different JVMs.

I wouldn't have a problem with exceptions being thrown on all JVMs. But
handling the exception on some JVMs, while letting it fly through on another,
that can not be the idea of writing portable code.

cheers,
  Roland

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message