You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2014/03/16 00:28:42 UTC

[jira] [Assigned] (OWB-941) Signal or handle differently final methods

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

Mark Struberg reassigned OWB-941:
---------------------------------

    Assignee: Mark Struberg

> Signal or handle differently final methods
> ------------------------------------------
>
>                 Key: OWB-941
>                 URL: https://issues.apache.org/jira/browse/OWB-941
>             Project: OpenWebBeans
>          Issue Type: New Feature
>          Components: New Features
>    Affects Versions: 1.2.2
>            Reporter: Ludovic PĂ©net
>            Assignee: Mark Struberg
>            Priority: Minor
>              Labels: features
>
> OWB does not properly handle final methods of classes.
> That leads to strange bugs, like discussed on this thread http://mail-archives.apache.org/mod_mbox/deltaspike-users/201403.mbox/browser
> In this case, there is
> public class Base implements Serializable {
>     public final List getValues() { ... }
> }
> @Named
> @ViewAccessScoped
> public class DerivedFromBase extends Base {
> }
> In my case, the method was called on the proxy rathered that on the base class when called through an EL expression like #{derivedFromBase.values}
> It would be nice if OWB would
> 1) scream if it encounters a "final" method. Refusing to create a proxy might be a bit harsh. Just not proxying the "final" method along with a log might be better (and easier to debug)
> or better
> 2) handle differently final methods



--
This message was sent by Atlassian JIRA
(v6.2#6252)