Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-167

Support @EJB.mappedName for TestClass injection

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 1.0.0.Alpha5
    • 1.0.0.Alpha2
    • Runtime Enricher SPI
    • None

    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)..

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. ARQ-340 mappedName and lookup attributes are ignored for @EJB in jections into test cases, forcing a naming convention on implementations

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users ARQ-223 Create a EJB test execution protocol

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Activity

            People

              drallendc@gmail.com David Allen (Inactive)
              aslak@redhat.com Aslak Knutsen
              Votes:
              2 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: