You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Göktürk Gezer (JIRA)" <ji...@apache.org> on 2013/02/04 19:44:14 UTC

[jira] [Resolved] (FELIX-3889) Excluding run-time visible annotations from custom handler processing

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

Göktürk Gezer resolved FELIX-3889.
----------------------------------

    Resolution: Fixed

Fixed by commit: http://svn.apache.org/viewvc/felix/trunk/ipojo/manipulator/manipulator/src/main/java/org/apache/felix/ipojo/manipulator/metadata/annotation/ClassMetadataCollector.java?rev=1442296&r1=1442295&r2=1442296&view=diff
                
> Excluding run-time visible annotations from custom handler processing
> ---------------------------------------------------------------------
>
>                 Key: FELIX-3889
>                 URL: https://issues.apache.org/jira/browse/FELIX-3889
>             Project: Felix
>          Issue Type: Improvement
>          Components: iPOJO
>            Reporter: Göktürk Gezer
>            Assignee: Göktürk Gezer
>            Priority: Minor
>
> Annotations those put to ipojo components along with @Component annotation are treated as custom handler annotations. This make it impossible to put annotations to components for other purposes.
> There are plenty of codes depend on reading run-time visible annotations at run-time. Due to current behavior of annotation processing we're lefting out those codes.
> Besides there is no point in making handler annotation runtime visible, since handler itself will already see those annotation in generated metadata. Also reading handler annotation's attributes at run-time is clear design inefficiency and does not worth to left out all existing codes depend on runtime visible annotations.
> Lefting out annotations with runtime retention policy at handler metadata generation will fix all those issues above.
> This change won't affect current IPojo code and any custom handler implementation I know of, though it'll improve the component's capability to engage with other 3th party codes mentioned above. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira