-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
1.0.0.Alpha1, 1.0.0.Alpha2
-
None
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.
- is blocked by
-
ARQ-910 JNDI lookup fails for @EJB mappedName when the bean has more instances
- Open
- is duplicated by
-
ARQ-93 No-interface session beans are not supported
- Closed
-
ARQ-975 Embedded glassfish 3.1 container supports only EJB with suffix "bean" in name
- Open
-
ARQ-92 EJB injection enricher should follow the EE 6 JNDI Standard
- Closed
- is related to
-
ARQ-317 EJB context lookup name does not follow the web context root name when they are part of the same WAR
- Open
- relates to
-
ARQ-1274 @EJB#lookup() support in EJBInjectionEnricher
- Closed
-
ARQ-836 Enricher does not lookup EJB successfully unless the name of deployed archive is "test" or beanName/mappedName attribute is set
- Open