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

[Pete Muir (JIRA)]

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

Pete Muir commented on CDI-362:
-------------------------------

Whilst the CDI client proxies may, in practice, proxy those methods, I can't find any evidence in the spec that they are *supposed* to do this (beyond the language we added in CDI 1.1, which we can still change). The language I found said that we only treat EJB business methods as CDI business method invocations (on which decoration, interception etc can happen), and that only EJB business methods can be things like producer methods. So, my initial reasoning is that CDI shouldn't proxy anything but EJB business methods (i.e. public methods) on no-interface session beans. If this is the case, then the validation should be the same as EJB, I think.
                
> 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