[
https://issues.apache.org/jira/browse/HTTPCLIENT-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCLIENT-873.
------------------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 4.1 Alpha1)
> CoreConnectionPNames/HttpConnectionParams are missing the bean class.
Actually there is HttpConnectionParamBean already. It must have been
overlooked. Inconsistent class names are unfortunate but something we will have
to live with until 5.0
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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
