aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ARIES-668) Proxy or weaving code should not mark added synthetic methods final
Date Fri, 03 Jun 2011 06:43:47 GMT

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

David Jencks resolved ARIES-668.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.4
         Assignee: Timothy Ward

rev 1130914.  Does this look ok?

> Proxy or weaving code should not mark added synthetic methods final
> -------------------------------------------------------------------
>
>                 Key: ARIES-668
>                 URL: https://issues.apache.org/jira/browse/ARIES-668
>             Project: Aries
>          Issue Type: Bug
>          Components: Proxy
>    Affects Versions: 0.3
>            Reporter: David Jencks
>            Assignee: Timothy Ward
>             Fix For: 0.4
>
>
> OpenWebBeans checks classes for proxyiability by among other things checking for final
methods.  The java.lang.reflect.Modifier class does not expose anything about synthetic methods
and reports synthetic final methods as final.  Although it's possible to get owb to work by
modifying the check to exclude synthetic methods, this puts the responsibility in a peculiar
place.  The OWB folks also claim that since java 5 marking methods final has no effect on
the ability of the jit to optimize method calls so there isn't really any reason to mark these
final.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message