[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=12765071#comment-12765071 ] 

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

[~pmuir] EJB spec is not final yet ;). Let's assume that the EJB spec will replace the "final" rule from 3.1 "All methods must not" to "Only private may".

There is also a 2nd problem (though not in the subject line) - which methods constitute the "view". EJB spec says public (3.2 now has non-static added), and the CDI spec says all non-static non-private. Which gives a wrong impression to the CDI users (and some containers) if they also use (support) EJBs, but didn't read *very carefully* the EJB spec.
                
> 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