Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-1680

Only one of two EJBs with equal class name gets discovered

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • 2.2.0.Alpha1
    • 2.1.2.Final
    • None
    • None

    Description

      If there are two session beans with the same class name in one EAR archive, in separate JARs, then Weld only discovers one of them, randomly.

      Example deployment scenario:

      test.ear
 |-- ejb-jar1.jar
   |-- p1.MyEjb.class
 |-- ejb-jar2.jar
   |-- p2.MyEjb.class

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. WFLY-3329 EJBs with same Java class name not intercepted by CDI interceptors

          • 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
          duplicates

          Bug - A problem that impairs or prevents the functions of the product. WELD-1586 Ambiguous dependency not detected for (two) session beans with the same name

          • 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.
          • Resolved

          Activity

            People

              mkouba@redhat.com Martin Kouba
              rsmeral Ron Šmeral (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: