[cdi-dev] [JBoss JIRA] (CDI-362) No-interface view EJB proxying rules are less strict than CDI, leading to odd error reporting

[Marina Vatkina (JIRA)]

    [ https://issues.jboss.org/browse/CDI-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765032#comment-12765032 ] 

Marina Vatkina commented on CDI-362:
------------------------------------

EJB 3.1 said "All methods of the bean class and any superclasses must not be declared final". We tried to relax this restriction, and it is definitely too harsh for private methods - you can't access them through proxy anyway. We can relax less, but there is no good reason to prevent final private methods.
                
> 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