[
https://issues.jboss.org/browse/CDI-527?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba commented on CDI-527:
----------------------------------
bq. as I already said many weeks ago...
Sometimes there is no good solution. Also for legacy applications this beans.xml approach
wouldn't help either - if it is possible to change the app, then in most cases the
"interface workaround" mentioned in A. might be used.
bq. And no, as discussed and agreed many times...
Not agreed. However, this issue is not a good place to discuss the problem. One of the
things which is not "perfectly covered" is merging of {{beans.xml}} within an
existing EE module.
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)