[
https://issues.apache.org/jira/browse/CONFIGURATION-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957600#comment-14957600
]
Oliver Heger commented on CONFIGURATION-611:
--------------------------------------------
I was hoping for a less invasive solution. The classes do what they are
supposed to do. There is a level of abstraction missing, but as was discussed,
this could be added later without breaking compatibility. So deprecating these
classes or even removing them would go to far IMHO.
As Commons Configuration is going to have a major release, there is the
possibility to have breaking changes. However, I would rather not strip a
feature of the older version if there is no replacement in the new version.
> Provide methods to create Beans without knowledge of the Configuration's
> implementation
> ---------------------------------------------------------------------------------------
>
> Key: CONFIGURATION-611
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-611
> Project: Commons Configuration
> Issue Type: Improvement
> Reporter: Jon Weygandt
> Priority: Minor
>
> The current method to create a bean uses a pattern that requires the user to
> know of the Configuration's implementation.
> (https://commons.apache.org/proper/commons-configuration/userguide/howto_beans.html#Declaring_and_Creating_Beans)
> It should be possible to decouple this dependency and have some
> implementation independent method.
> One proposal would be to extend the BeanHelper code to implement this in a
> general way.
> Another proposal would be to have an interface that Configurations could
> extend to get the BeanDeclaration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
