[OWB-942] CLONE owb-1.2- Signal or handle differently final methods

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.2.2
• Fix Version/s: 1.5.0
• Component/s: New Features
• Labels: features
• Assignee: Mark Struberg
• Reporter: Ludovic Pénet
• Created: 16/Mar/14 08:03
• Updated: 19/Apr/15 14:53
• Resolved: 16/Mar/14 08:06

Description

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

Issue Links

• is a clone of: OWB-941 Signal or handle differently final methods