You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tamaya.apache.org by "Anatole Tresch (JIRA)" <ji...@apache.org> on 2017/02/23 00:38:45 UTC

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

     [ https://issues.apache.org/jira/browse/TAMAYA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anatole Tresch reassigned TAMAYA-197:
-------------------------------------

    Assignee: Anatole Tresch

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