You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Jens Wike (JIRA)" <ji...@apache.org> on 2007/12/20 18:22:42 UTC
[jira] Created: (HTTPCLIENT-722) API: Configuration framework is
not Java-like
API: Configuration framework is not Java-like
---------------------------------------------
Key: HTTPCLIENT-722
URL: https://issues.apache.org/jira/browse/HTTPCLIENT-722
Project: HttpComponents HttpClient
Issue Type: Bug
Affects Versions: 4.0 Alpha 2
Reporter: Jens Wike
I consider the new configuration scheme a major draw back.
Having a map and introducing static accessor methods for this map
is neither OO nor Java-like.
Configuration data should be standard beans compliant classes.
Also a JSR250 compliant annotation should be there (@Resource, et. al.)
This way http client and its configuration can assembled directly in an
IoC container.
--
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
[jira] Resolved: (HTTPCLIENT-722) API: Configuration framework is
not Java-like
Posted by "Roland Weber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPCLIENT-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roland Weber resolved HTTPCLIENT-722.
-------------------------------------
Resolution: Invalid
If you don't like the API we've designed, feel free to open a discussion on the mailing list, or even a JIRA ticket as "Wish" or "Improvement". But your not liking one of our design decisions is most certainly NOT a bug. At least not on our side.
HttpCore-main uses Java 1.3, the @tag stuff hasn't been introduced until Java 5.0. You request is invalid.
We can't use standard beans class for holding configuration data, because then we'd need to know in advance what parameters we need to support. A map can hold all kinds of parameters, and the same map can be passed to and used in various places of the framework.
Some beans stuff has been introduced recently to address Spring integration, maybe you'll like that better. See HTTPCORE-37.
cheers,
Roland
> API: Configuration framework is not Java-like
> ---------------------------------------------
>
> Key: HTTPCLIENT-722
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-722
> Project: HttpComponents HttpClient
> Issue Type: Wish
> Affects Versions: 4.0 Alpha 2
> Reporter: Jens Wike
>
> I consider the new configuration scheme a major draw back.
> Having a map and introducing static accessor methods for this map
> is neither OO nor Java-like.
> Configuration data should be standard beans compliant classes.
> Also a JSR250 compliant annotation should be there (@Resource, et. al.)
> This way http client and its configuration can assembled directly in an
> IoC container.
--
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
[jira] Updated: (HTTPCLIENT-722) API: Configuration framework is
not Java-like
Posted by "Ortwin Glück (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HTTPCLIENT-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ortwin Glück updated HTTPCLIENT-722:
------------------------------------
Issue Type: Wish (was: Bug)
Jens, would you mind joining the discussion on our developer mailing about design issues like this one. The bug tracking is not such a good forum tool.
> API: Configuration framework is not Java-like
> ---------------------------------------------
>
> Key: HTTPCLIENT-722
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-722
> Project: HttpComponents HttpClient
> Issue Type: Wish
> Affects Versions: 4.0 Alpha 2
> Reporter: Jens Wike
>
> I consider the new configuration scheme a major draw back.
> Having a map and introducing static accessor methods for this map
> is neither OO nor Java-like.
> Configuration data should be standard beans compliant classes.
> Also a JSR250 compliant annotation should be there (@Resource, et. al.)
> This way http client and its configuration can assembled directly in an
> IoC container.
--
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