[
https://issues.jboss.org/browse/CDI-527?page=com.atlassian.jira.plugin.sy...
]
Romain Manni-Bucau commented on CDI-527:
----------------------------------------
Think D is just not realistic enough to be reliable on the long term (+ better is the spec
doesnt get 100 pages of whitelist/blackist ;))
C sounds overkill for this particular and precise need
I hesitate between A and B cause B gives the ability to just code "java" which
is nice. Now I never saw an application seeing this as a real issue/blocker (means when it
happens the reaction is: "ah? not allowed, ok let's do this other way") so A
would work fine with a very low cost.
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)