[
https://issues.apache.org/jira/browse/CONFIGURATION-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved CONFIGURATION-165.
----------------------------------------
Resolution: Won't Fix
This issue is now open for a long while. ATM I see no really benefit in
changing the conversion code to use beanutils. The additional dependency may
even be considered as harmful by some people. Maybe if the converters in
beanutils are enhanced to cover all the use cases we need, or if the [convert]
project wakes up again, we can re-evaluate this issue.
So closing this ticket as won't fix.
> [configuration] Use beanutils for conversions
> ---------------------------------------------
>
> Key: CONFIGURATION-165
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-165
> Project: Commons Configuration
> Issue Type: Improvement
> Environment: Operating System: other
> Platform: Other
> Reporter: Ittay Dror
> Priority: Minor
>
> Currently AbstractConfiguration has its own logic for conversion. This makes
> it
> non standard with commons beanutils. Furthermore, commons beanutils is
> extendible, so by using it, one can write a method
> Object getProperty(String key, Class c)
> which would automatically convert the returned value of getProperty(String
> key)
> to the requested class. This means that (as long as I register the right
> converter) i can use getProperty("my.class", MyClass.class) and get
> automatically and instance of MyClass. Very usefull, esp. for enumerations
> (which can easily have their own converter if using commons-lang's enum)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
