]
Pedro Kowalski commented on ARQ-77:
-----------------------------------
Any progress about this task?
Recently I had to inject EJB's using it's local business interface which had 2
implementations (none of them was resolved by simply adding "Bean" suffix), so
in order to make it working I had to do some dirty hacks with 'mappedBy'
attribute.
We could add the 'beanName' attribute-awareness to the EJB-enricher (similarly to
the mappedBy), but I don't know if it does make any sense if more heavy refactoring is
supposed to happen?
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: