[jira] [Commented] (TAMAYA-197) DefaultConfigurationInjector does not inject into superclasses' fields

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

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

Commit abb34d65181d9be614cbba258dd0ee174a7f3b7d 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=abb34d6 ]

TAMAYA-197: Fixed bug not injecting properties in superclasses.


> DefaultConfigurationInjector does not inject into superclasses' fields
> ----------------------------------------------------------------------
>
>                 Key: TAMAYA-197
>                 URL: https://issues.apache.org/jira/browse/TAMAYA-197
>             Project: Tamaya
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 0.3-incubating
>            Reporter: Thomas Liebetraut
>            Assignee: Anatole Tresch
>             Fix For: 0.3-incubating
>
>         Attachments: TAMAYA-197.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> The current implementation of tamaya-inject won't inject configuration into superclasses' values.
> Suppose a class A with some @Config annotated members and a class B which extends A. Then {{ConfigurationInjection.getConfigurationInjector().configure(instanceOfB);}} won't configure any fields annotated in A.
> Also, because the runtime time is used to determine what to inject, there is no easy way to get around this from the user API.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)