[
https://issues.jboss.org/browse/CDI-362?page=com.atlassian.jira.plugin.sy...
]
Romain Manni-Bucau commented on CDI-362:
----------------------------------------
Yes, i think almost all containers implemented the link between CDI and EJB through
"another proxy" so basically the EJB proxy will prevent more than what is
allowed in CDI + final methods are forbidden in EJBs too (even public)
No-interface view EJB proxying rules are less strict than CDI,
leading to odd error reporting
---------------------------------------------------------------------------------------------
Key: CDI-362
URL:
https://issues.jboss.org/browse/CDI-362
Project: CDI Specification Issues
Issue Type: Bug
Reporter: Pete Muir
Fix For: 1.1.FD
E.g.
// allowed by EJB
// disallowed by CDI
@Stateful @RequestScoped
public class MyBean {
final void m() { };
}
public class Other {
@EJB MyBean field; // PASS
@Inject MyBean field; // FAIL - unproxyable
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira