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

Messaging should not expose its subsystem module to deployments

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 20.0.0.Final
    • Fix Version/s: None
    • Component/s: JMS
    • Labels:
      None

      Description

      The messaging-activemq subsystem exposes its subsystem module to the deployment classloader.  According to comments, this was done to allow CDI to load the requisite portable extension to support JMSContext injection.  This is a very bad idea, as the deployment can then access all of the subsystem internals (including its dependents).

      The correct way to do this is to create a separate module containing userspace classes, including the CDI extension and its dependents.  Only this module should ever be exposed to deployments.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                pferraro Paul Ferraro
                Reporter:
                pferraro Paul Ferraro
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: