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

[Aslak Knutsen (JIRA)]

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

Aslak Knutsen commented on ARQ-77:
----------------------------------

No, EJB injection outside of a CDI enabled deployment is still based on guessing names. But only relevant to older containers as CDI is enabled by default in EE7

> 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 was sent by Atlassian JIRA
(v6.4.11#64026)