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

Make ejb3 extension dependency on org.jboss.as.remoting optional

    Details

    • Type: Enhancement
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 21.0.0.Beta1
    • Component/s: EJB
    • Labels:
      None

      Description

      This is part of an overall effort to eliminate non-optional dependencies on the org.jboss.as.remoting module. Both because depending on extension modules has a code smell but specifically because the org.jboss.as.remoting module brings in fairly large dependency tree.

      The ejb3 subsystem has two general categories of use of the org.jboss.as.remoting module:

      1) A number of child resources use it. The ResourceDefinition for those can use registerAdditionalRuntimePackages to record a hard dependency allowing the module.xml to make it optional.

      2) AbstractOutboundConnectionService is used by deployment code not limited to particular child resource. But once WFCORE-4955 is done and integrated this can be replaced with use of the new interface from the org.jboss.as.network module with injection done using the capability.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  yersan Yeray Borges Santana
                  Reporter:
                  brian.stansberry Brian Stansberry
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: