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

Deployments using RMI Java Naming provider must define explicit dependency on jdk.naming.rmi JPMS module

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 28.0.0.Final
    • None
    • JMX, Test Suite
    • None
    • ---
    • ---

    Description

      Deployments relying on internal JDK APIs / features need to declare an explicit dependency on particular Java SE internal JPMS module prividing that API / feature.

      For example in this concrete case to enable JNDI over RMI JDK feature jdk.naming.rmi module must be added:

       * either to deployment manifest 'Depencencies' attribute

       * or to the jboss-deployment-structure.xml 'jboss-deployment-structure/deployment/dependencies' element

      Attachments

        Issue Links

          is depended on by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFCORE-6249 Eliminate usage of deprecated sun.jdk module

          • 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

          Activity

            People

              ropalka Richard Opalka
              ropalka Richard Opalka
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: