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 2009/09/04 23:18:57 UTC
[jira] Updated: (HTTPCLIENT-873)
CoreConnectionPNames/HttpConnectionParams doesn't have a corresponding Bean
class
[ https://issues.apache.org/jira/browse/HTTPCLIENT-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski updated HTTPCLIENT-873:
-----------------------------------------
Fix Version/s: 4.1.0
Gerald,
Can you put together a patch for this issue?
Oleg
> CoreConnectionPNames/HttpConnectionParams doesn't have a corresponding Bean class
> ---------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-873
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-873
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 4.0 Final
> Reporter: Gerald Turner
> Priority: Minor
> Fix For: 4.1.0
>
>
> The HttpParams framework seems to follow a policy of having:
> • an interface to declare the parameter string constant (e.g. ConnManagerPNames.TIMEOUT), also AllPNames implements this interface.
> • a class containing static accessors for the parameter (e.g. ConnManagerParams.get/setTimeout)
> • a bean class with accessors (sometimes setters only) for the parameter (e.g. ConnManagerParamBean.setTImeout)
> CoreConnectionPNames/HttpConnectionParams are missing the bean class.
> Furthermore the class name HttpConnectionParams doesn't quite follow the style (should be named CoreConnectionParams), but ClientPNames/HttpClientParams also has this oddity.
--
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