[arquillian-issues] [JBoss JIRA] Issue Comment Edited: (ARQ-77) Support @EJB injection with proper semantics
[
https://issues.jboss.org/browse/ARQ-77?page=com.atlassian.jira.plugin.sys...
]
Aslak Knutsen edited comment on ARQ-77 at 9/5/11 11:58 AM:
-----------------------------------------------------------
There is currently nothing we can do with the EJB enrichment without getting hooks into
all EJB Containers(not going to happen over night).
Something like:
@EJB(beanName="MyTestBean")
private TestBean bean;
Could attempt to lookup:
java:/module/MyTestBean!TestBean
java:/module/MyTestBean
?
was (Author: aslak):
There is currently nothing we can do with the EJB enrichment without getting hooks
into all EJB Containers(not going to happen over night).
Something like:
@EJB(beanName="MyTestBean")
private TestBean bean;
Could attempt to lookup:
java:/module/beanName!TestBean
java:/module/beanName
?
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