You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Allen Hackley (JIRA)" <ji...@apache.org> on 2009/12/12 19:59:18 UTC

[jira] Commented: (FELIX-1941) Make @Requires and any other appropriate annotations inheritable. (Add @Inherited meta-annotation to the annotation definition)

    [ https://issues.apache.org/jira/browse/FELIX-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789778#action_12789778 ] 

Allen Hackley commented on FELIX-1941:
--------------------------------------

It occurs to me that there may arise a scenario where one does not want to inherit the parent field annotations, and so some functionality would need to be added to optionally disable it from occurring.

> Make @Requires and any other appropriate annotations inheritable. (Add @Inherited meta-annotation to the annotation definition)
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-1941
>                 URL: https://issues.apache.org/jira/browse/FELIX-1941
>             Project: Felix
>          Issue Type: Wish
>          Components: iPOJO
>    Affects Versions: iPOJO-1.4.0
>            Reporter: Allen Hackley
>
> Take the following scenario.
> - Class A and Class B have the same superclass: Class C
> - Class C has one or more fields common to both A and B, to minimize having to write redundant code.
> - Classes A and B are declared to be component types.
> - iPOJO currently will not perform field injection on any of the inherited fields within Class A or Class B, even if Class C is also a component type that explicitly exposes those fields.
> - This results in having to write some combination of xml/annotations/java for each individual inherited field, within each individual subclass of C, which defeats the purpose of avoiding redundant code.
> I have written my own implementation of @Requires that is identical to the original, with the exception of the @Inherited annotation, and this seems to solve the above problem.  It would be nice if it were integrated into the iPOJO core.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.