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

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

A *compliant* EJB container should proxy only public methods of a bean with a no-interface view. If it does, only public bean methods invocations would go through the EJB container, i.e. handling of transaction/interceptor/security will be performed only for the public methods. Any other method invocation would go directly to the bean class. Probably all protected or package private methods on a no-interface bean should have been disallowed (it's too late now) because they produce a dangerous situation - they are available on the proxy, but shouldn't be called through it.
                
> 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