Details
-
Type:
Feature Request
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 1.0.0.Alpha2
-
Fix Version/s: 1.0.0.Alpha5
-
Component/s: Runtime Enricher SPI
-
Labels:None
-
Forum Reference:
-
Affects:Documentation (Ref Guide, User Guide, etc.)
Description
We should support letting the user set the mappedName on the injection in the test case to avoid having to follow our naming standards. (until we can do it more reliable, https://jira.jboss.org/browse/ARQ-77)
Needs to document the potential jndi naming changes between Embedded EJB containers and Remote Containers(packaging)..
Gliffy Diagrams
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
To work as expected we cant rewrite the deployments. need 'native' EJB test execution.
Aslak Knutsen
added a comment - To work as expected we cant rewrite the deployments. need 'native' EJB test execution. This should be finished other than documentation updates. A preliminary view pending documentation is at git://github.com/drallen/arquillian.git. Nothing special, mappedName is used as provided to do JNDI lookup. The user is responsible for ensuring that this is the correct name of the bean as deployed in the container being tested.
David Allen
added a comment - This should be finished other than documentation updates. A preliminary view pending documentation is at git://github.com/drallen/arquillian.git. Nothing special, mappedName is used as provided to do JNDI lookup. The user is responsible for ensuring that this is the correct name of the bean as deployed in the container being tested. pushed upstream master
Aslak Knutsen
added a comment - pushed upstream master I still haven't updated the docs for this yet. I was going to do that today.
David Allen
added a comment - I still haven't updated the docs for this yet. I was going to do that today. 
I really think this will help with the adoption of Arquillian when it comes to testing legacy systems.
This feature would make my day