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

[Pedro Kowalski (JIRA)]

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

Pedro Kowalski edited comment on ARQ-77 at 9/6/11 5:40 AM:
-----------------------------------------------------------

Yeah, that's exactly what I was thinking of - to support at least some of the portable JNDI, so:

java:module/<bean-name>[!<fully-qualified-interface-name>]

EDIT: Oh, and I guess that if one specifies both - mappedName and beanName it should throw an exception, as I don't see real use of specifying both values at the same time, right?

      was (Author: PedroKowalski):
    Yeah, that's exactly what I was thinking of - to support at least some of the portable JNDI, so:

java:module/<bean-name>[!<fully-qualified-interface-name>]
  
> 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 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira