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

2018-07-10 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/TAMAYA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 


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


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

2018-07-10 Thread ASF subversion and git services (JIRA)


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

ASF subversion and git services commented on TAMAYA-336:


Commit f5d49016fcfb31ed44a14ff76abe9d1a422884c1 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=f5d4901
 ]

TAMAYA-336 Added javadoc.


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


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

2018-07-10 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/TAMAYA-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)


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

2018-04-29 Thread Harald Wellmann (JIRA)

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

Harald Wellmann commented on TAMAYA-336:


{{org.apache.tamaya.inject.internal.DefaultConfigurationInjector.createTemplate(Class,
 Configuration)}} never actually uses the {{Configuration}} parameter.

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