[weld-issues] [JBoss JIRA] Updated: (WELD-290) Injected stateless EJBs cause failed proxability

[Andy Gibson (JIRA)]

     [ https://jira.jboss.org/jira/browse/WELD-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Gibson updated WELD-290:
-----------------------------

    Attachment: weldear.ear


This is an EAR project (containing source) that demonstrates the problems of injecting a Stateless EJB into a simple Weld managed bean with a passivating (Session/Conversation) scope. 

To get the error, simply deploy it. To see the problem 'go away' change the scoped of the SimpleBean class (in the war file) to @RequestScoped or @ApplicationScoped. 

This ear deploys fine on Glassfish v3 build 71+, but not on JBoss 5.20 Beta. If deployed on JBoss, this could prove whether the problem is in Glassfish or a general weld problem since so far, the problem has only been seen on Glassfish because I can't deploy it on JBoss, and there is the question of whether EJBs in a WAR file are actually deployed as EJBs.



> Injected stateless EJBs cause failed proxability
> ------------------------------------------------
>
>                 Key: WELD-290
>                 URL: https://jira.jboss.org/jira/browse/WELD-290
>             Project: Weld
>          Issue Type: Bug
>          Components: Bootstrap and Metamodel API
>    Affects Versions: 1.0.0.GA
>            Reporter: Nicklas Karlsson
>         Attachments: weldear.ear
>
>
> The validation checks for proxability checks if the injected beans are proxyable. This is incorrectly done with isProxyable() for EJB:s (which return false for stateless EJBs). A stateless EJB is not proxyable itself but should be considered proxyable if injected.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira