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

The org.jboss.resteasy.microprofile.config is not applied to deployments

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 27.0.0.Final
    • None
    • MP Config, REST
    • None
    • Workaround Exists
    • Hide

      Add the module as a global module.

      CLI
      /subsystem=ee:write-attribute(name=global-modules, value=[{name=org.jboss.resteasy.microprofile.config, services=true}])
      Show
      Add the module as a global module. CLI /subsystem=ee:write-attribute(name=global-modules, value=[{name=org.jboss.resteasy.microprofile.config, services= true }])
    • ---
    • ---

      The org.jboss.resteasy.microprofile.config module is in WildFly, however it's not exported to deployments. In the RESTEasy galleon pack module the exports this module as an optional module dependency.

      <!-- Optional dependencies if we have the MicroProfile Config available. Note we need to export the
     org.jboss.resteasy.microprofile.config as it will be loaded from another module loader.
 -->
<module name="org.eclipse.microprofile.config.api" optional="true"/>
<module name="org.jboss.resteasy.microprofile.config" export="true" services="export" optional="true"/>

      Something similar should be done in WildFly. This can be done either via the org.jboss.resteasy.resteasy-core module like in the RESTEasy galleon pack or it needs to be added to deployments via a DUP.

      Note too that while doing this the module name should be removed LayersTestCase.NOT_USED_COMMON array as it should be added correctly after this change.

              jperkins-rhn James Perkins
              jperkins-rhn James Perkins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: