[
https://issues.apache.org/jira/browse/CONFIGURATION-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636831#action_12636831
]
Oliver Heger commented on CONFIGURATION-337:
--------------------------------------------
Patch applied in revision 701654.
It could even be slightly simplified. As it turned out, defining a custom
CombinedConfiguration class as resulting configuration is already supported.
This is due to the bean definition mechanism, which automatically looks for a
config-class attribute and evaluates it if present; otherwise the default class
passed to the BeanHelper is used. Also at the creation of the providers there
is no need to explicitly specify the provider class because it is found
automatically by the XMLBeanDeclaration.
Leaving open until the patch was ported to the configuration-2 branch.
> Allow users of DefaultConfigurationBuilder to configure the class name of
> the CombinedConfiguration to create and to configure providers
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CONFIGURATION-337
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-337
> Project: Commons Configuration
> Issue Type: Improvement
> Affects Versions: 1.6
> Environment: Any
> Reporter: Ralph Goers
> Fix For: 1.6
>
> Attachments: config.patch, config2.patch
>
>
> This enhancement allows config-class to be specified on the result element.
> The specified class must extend CombinedConfiguration.
> This enhancment allows ConfigurationProviders to be configured by adding
> <providers>
> <provider tag="myprovider" config-class="MyProviderClass"/>
> </providers
> to the header.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
