[
https://issues.apache.org/jira/browse/CONFIGURATION-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953491#comment-14953491
]
Jon Weygandt commented on CONFIGURATION-611:
--------------------------------------------
The more I look into what I wanted to do with Beans, the more I realize that
this type of pattern is not really necessary. For this reason I will be OK with
this being Resolved as "Won't Fix".
As Oliver noted in emails this was used internally, and exposed publicly as it
seemed useful. I wonder how many are using it? It may be that the documentation
made this look too important, and the use of it will tie one to XML, which may
not be desired.
> 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)
