[
https://issues.jboss.org/browse/CDI-362?page=com.atlassian.jira.plugin.sy...
]
Jozef Hartinger edited comment on CDI-362 at 4/4/13 5:41 AM:
-------------------------------------------------------------
{quote}Actually the EJB spec is very strict "Attempted invocations of methods with
any other access modifiers via the no-interface view reference must result in the
javax.ejb.EJBException"{quote}
Assuming a protected method is final how do you detect that it was invoked? Where do you
place the piece to throw EJBException? You obviously cannot have a proxy wrap the method
call.
was (Author: jharting):
{quote}Actually the EJB spec is very strict "Attempted invocations of methods
with any other access modifiers via the no-interface view reference must result in the
javax.ejb.EJBException"{quote}
Assuming a protected method is final how do you detect that it was invoked? Where do you
place the piece to throw EJBException?
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