Uploaded image for project: 'RESTEasy'
  1. RESTEasy
  2. RESTEASY-2406

Incorporate MicroProfile Config in RESTEasy

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 3.12.0.Final
    • 3.9.1.Final
    • None
    • None
    • Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration
    • Low

    Description

      Currently, RESTEasy 3.x (targeted to Wildfly) uses servlet context-params to obtain configuration information. In RESTEasy 4.x, we have updated configuration to access all standard MicroProfile Config sources. Also, we have added three additional ConfigSources:

      • servlet init-params (ordinal 60)
      • filter init-params (ordinal 50)
      • servlet context-params (ordinal 40)

      In this feature request, we propose to port the relevant changes from RESTEasy 4.x to RESTEasy 3.x.

      Attachments

        Issue Links

          incorporates

          Enhancement - An enhancement or refactoring of existing functionality RESTEASY-1312 Document resteasy.servlet.mapping.prefix as init-param

          • 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
          is cloned by

          Feature Request - Feature requests from customers and/or users WFLY-12779 Incorporate MicroProfile Config in RESTEasy

          • 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
          relates to

          Bug - A problem which impairs or prevents the functions of the product. RESTEASY-2915 Disable some MicroProfile tests with prepared MicroProfileDependent category

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: RESTEASY

              People

                rsigal@redhat.com Ronald Sigal
                rsigal@redhat.com Ronald Sigal
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: