[
https://issues.apache.org/jira/browse/CONFIGURATION-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved CONFIGURATION-551.
----------------------------------------
Resolution: Fixed
Data type conversions are now handled by an object implementing the simple
{{ConversionHandler}} interface. It is possible for applications to provide a
custom {{ConversionHandler}} implementation (either by creating a new
implementation from scratch or by extending the {{DefaultConversionHandler}}
class). This way the conversion mechanism can be adapted and/or extended.
> Make data type conversions extensible
> -------------------------------------
>
> Key: CONFIGURATION-551
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-551
> Project: Commons Configuration
> Issue Type: Improvement
> Components: Type conversion
> Affects Versions: 1.9
> Reporter: Oliver Heger
> Fix For: 2.0
>
>
> So far, a fix set of data type conversions is supported. Some are available
> directly in the {{Configuration}} interface (especially for primitive and
> standard Java types), others are provided by {{DataConfiguration}}.
> Currently, it is not easy possible for client applications to customize type
> conversions or add new converters.
> I am not sure whether we should go so far to implement yet another framework
> with type converters; at least not directly for version 2.0. However, there
> should be at least possibilities to hook into the conversion mechanism.
> Ideally, I would like to have a simple facade handling the different kinds of
> conversions. By providing alternative implementations, client applications
> should be able to adapt type conversions or even plug in a different
> conversion framework, e.g. Commons Beanutils.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
