Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11870

abstract classes with @EJB annotation included in libraries will cause deployment failures

    Details

    • Steps to Reproduce:
      Hide

      Use the attached Reproducer (not for build) and deploy the war files
      slsbInjection/web-1/target/ejb31-Injection-web1.war
      -> working
      slsbInjection/web-2/target/ejb31-Injection-web2.war
      -< deployment failure

      Show
      Use the attached Reproducer (not for build) and deploy the war files slsbInjection/web-1/target/ejb31-Injection-web1.war -> working slsbInjection/web-2/target/ejb31-Injection-web2.war -< deployment failure
    • Affects:
      Migration, Compatibility/Configuration, User Experience

      Description

      If an archive include libraries with interfaces and abstract classes the deployment will fail if there are annotations for injection like @EJB.
      Only if the injected EJB is available within the deployed file (or any other deployment) it is possible to deploy it.

      As the abstract class can not cause any instance the failure does not make sense.
      Also former versions are deploying the same file correct and work fine.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  thofman Tomas Hofman
                  Reporter:
                  wdfink Wolf-Dieter Fink
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: