[
https://issues.apache.org/jira/browse/TAMAYA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538697#comment-16538697
]
ASF subversion and git services commented on TAMAYA-336:
--------------------------------------------------------
Commit 092869379985c12315519d4e99e4ed2b198d8349 in
incubator-tamaya-extensions's branch refs/heads/configjsr from [~anatole]
[
https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=0928693
]
TAMAYA-336 Fixed config templates.
Signed-off-by: Anatole Tresch <[email protected]>
> Configuration templates do not work with custom configurations
> --------------------------------------------------------------
>
> Key: TAMAYA-336
> URL: https://issues.apache.org/jira/browse/TAMAYA-336
> Project: Tamaya
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 0.3-incubating
> Reporter: Harald Wellmann
> Assignee: Anatole Tresch
> Priority: Major
>
> h3. Scenario
> I'm building a configuration template from an interface, passing a custom
> configuration as a parameter. This configuration differs from the default
> configuration obtained by {{ConfigurationProvider.getConfiguration()}}.
> {code}
> AppConfiguration appConfig = ConfigurationInjection.getConfigurationInjector()
> .createTemplate(AppConfiguration.class, customConfiguration);
> {code}
> h3. Expected Behaviour
> {{appConfig}} returns values from the {{customConfiguration}}.
> h3. Actual Behaviour
> {{appConfig}} returns values from the default configuration.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
