hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jens Wike (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (HTTPCLIENT-721) API: HttpException should inherit from IOException
Date Thu, 20 Dec 2007 17:47:43 GMT

     [ https://issues.apache.org/jira/browse/HTTPCLIENT-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jens Wike reopened HTTPCLIENT-721:


> different causes and may need different handling

Of you course you can handle it different also when in the IOException hierarchy, if you
want and can handle it at all.

It is common practice in the Java API to have any I/O related exception under IOException,
examples: java.net.MalformedURLException, java.io.ObjectStreamException, java.util.ZipException.
These have nothing to do with any low-level I/O problems as you mentioned.

Adding additional hierarchies must be avoided, because it leads to a "rethrow pollution"
of the application code.

> API: HttpException should inherit from IOException
> --------------------------------------------------
>                 Key: HTTPCLIENT-721
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-721
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>    Affects Versions: 4.0 Alpha 2
>            Reporter: Jens Wike
> The description of IOException reads:
>  * Signals that an I/O exception of some sort has occurred. This
>  * class is the general class of exceptions produced by failed or
>  * interrupted I/O operations.
> This means HttpException and its subclasses _is_ an I/O Exception
> by the definition above. There is no need to have a separate Exception
> hierarchy.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message