[
https://issues.jboss.org/browse/CDI-527?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-527:
-----------------------------------
Martin, to come back to your argument that it won't help for legacy apps. It would not
help if you have a sealed WAR/EAR anymore which you cannot change. But you can add a
simple small jar to them which contains just the beans.xml with those additional settings
almost always. You can even put this into the shared classpath without changing your
EAR/WAR...
So I think it is the closest we can get. Again: happy for any other good solution. But
doing nothing is not an option in my opinion.
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)