[arquillian-issues] [JBoss JIRA] (ARQ-77) Support @EJB injection with proper semantics

[Arnold Johansson (JIRA)]

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

Arnold Johansson commented on ARQ-77:
-------------------------------------

So the pull-request has been pushed upstream by Aslak about a year ago. Great! -But when/where is the solution out? I for one think this is one of the more vital cases that neddes to be sorted and released as lots of organizations really want to use the otherwise excellent Arquillian but just can't due to this (@Inject just isn't an option).
                
> Support @EJB injection with proper semantics
> --------------------------------------------
>
>                 Key: ARQ-77
>                 URL: https://issues.jboss.org/browse/ARQ-77
>             Project: Arquillian
>          Issue Type: Bug
>          Components: GlassFish Containers, JBoss AS Containers, OpenEJB Containers, Packaging Enricher SPI
>    Affects Versions: 1.0.0.Alpha1, 1.0.0.Alpha2
>            Reporter: Andrew Rubinger
>            Assignee: Andrew Rubinger
>            Priority: Critical
>
> Tests should be able to have class or instance members injected according to @EJB semantics, avoiding the need for lookup code.  The prototype is currently in the OpenEJB integration module, but really we should have some EJB 3.1 Global JNDI syntax compatible resolvers (which need an EJB name, module name, app name, and business interface name).  Note that portable JNDI is under java:global, so only accessible to local JVMs.

--
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