[
https://issues.jboss.org/browse/CDI-527?page=com.atlassian.jira.plugin.sy...
]
Matej Novotny commented on CDI-527:
-----------------------------------
+1 for IgnoreFinalMethodProxying
Reasons:
* there is no real proxying going on for final methods, so word like {{ignore}} is better
than {{allow}}
* mentions that this annotation relates to final methods, making it clear
* another good fit is {{IgnoreUnproxyableMethod}}, though I deem
{{IgnoreFinalMethodProxying}} better because it underlines that you aim to ignore the
process of proxy creation (rather than ignoring the method)
allow proxying of classes with non-private final methods
--------------------------------------------------------
Key: CDI-527
URL:
https://issues.jboss.org/browse/CDI-527
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Beans
Affects Versions: 1.2.Final
Reporter: Mark Struberg
Assignee: Mark Struberg
Fix For: 2.0 (proposed)
Currently we explicitly disallow proxying of classes with non-private final methods.
EJB _does_ allow this. And there are a few final methods in the JDK and other libs. E.g.
HashMap#initHashSeedAsNeeded. Currently we cannot have a producer method for it.
We might rethink our decision and allow it. Probably with an own annotation like
@AllowProxying which disables this check for certain cases (subclass managed-beans or
producers).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)