[
https://issues.apache.org/jira/browse/HTTPCLIENT-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600901#action_12600901
]
Oleg Kalnichevski commented on HTTPCLIENT-779:
----------------------------------------------
Sam,
I think it is a pretty bad idea to re-throw protocol exceptions as a plain
vanilla IOException. Could you please create a special subclass of IOException,
ClientProtocolException or some such, for that end? I still would like to have
an option to catch protocol exceptions thrown by the HttpClient#execute method.
Oleg
> toplevel exception cleanup
> --------------------------
>
> Key: HTTPCLIENT-779
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-779
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Affects Versions: 4.0 Alpha 4
> Reporter: Sam Berlin
> Fix For: 4.0 Beta 1
>
> Attachments: httpclient-exception-cleanup.txt
>
>
> HttpClient.execute should throw only one exception, for easier general use.
> HttpMethod constructors (HttpGet, HttpPut, etc..) should throw
> IllegalArgumentException in the string constructor (imply the string is
> pre-checked). People wanting to see a URIException can use 'new HttpGet(new
> URI(uri))' and trigger the exception from the explicit URI creation.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
