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

EjbServices should be a per-module/BDA service

    XMLWordPrintable

Details

    Description

      The reason is that org.jboss.weld.ejb.spi.EjbDescriptor provides no unique identifier within an entire Java EE application.

      ejb-name does not have to be unique - see also the EJB spec (ejb-jar.xml XSD):

      The ejb-name element contains the name of an enterprise bean. The name must be unique within the ejb-jar file or .war file.

      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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. WELD-1700 EjbRequestContext not registered unless EjbServices added per-deployment

          • 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
              mkouba@redhat.com Martin Kouba
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: