You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2008/06/01 23:31:44 UTC
[jira] Resolved: (HTTPCLIENT-780) ProxyHost/HttpHost: Checks for
null when javadoc document null ok
[ https://issues.apache.org/jira/browse/HTTPCLIENT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPCLIENT-780.
------------------------------------------
Resolution: Fixed
Fix Version/s: 3.1.1
David,
I fixed javadocs in the SVN trunk, but it is very unlikely there is going to be another public release of the 3.x codeline.
Oleg
> ProxyHost/HttpHost: Checks for null when javadoc document null ok
> -----------------------------------------------------------------
>
> Key: HTTPCLIENT-780
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-780
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 3.1 Final
> Environment: N/A
> Reporter: David J. M. Karlsen
> Priority: Critical
> Fix For: 3.1.1
>
>
> The constructor javadocs for ProxyHost and HttpHost all state that null is an allowed value - but there's an check in the HttpHost constructor for this which throws IllegalArgumentException.
> (Actually allowing null as documented would also allow for a spring wiring remaining the same when using a proxy or not - steering the values from a propertyfile.)
--
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