You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/07/10 14:33:00 UTC

[jira] [Commented] (TAMAYA-336) Configuration templates do not work with custom configurations

    [ https://issues.apache.org/jira/browse/TAMAYA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16538691#comment-16538691 ] 

ASF subversion and git services commented on TAMAYA-336:
--------------------------------------------------------

Commit 54351ccb3df31da60db456b18491533bd2b8b5b6 in incubator-tamaya-extensions's branch refs/heads/master from [~anatole]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=54351cc ]

TAMAYA-336 Now forwarding target config instance.


> 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)