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

Add six new RESTEasy context parameters

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Major
    • None
    • None
    • REST
    • None

    Description

      New context parameters were introduced in

      • RESTEASY-2782: "resteasy.original.webapplicationexception.behavior"
      • RESTEASY-2849: "resteasy.patchfilter.legacy"
      • RESTEASY-2866: "resteasy.proxy.implement.all.interfaces"

      These can currently be set only as servlet context parameters. New attributes should be introduced to the JAX-RS subsystem which will be applied to all deployed applications. This avoids the user from having to set the parameter for each deployment.

      Attachments

        Issue Links

          is related to

          Feature Request - Feature requests from customers and/or users RESTEASY-2849 JsonPatch using jakarta.json-api

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-2646 Cache implementation in class RootNode is vulnerable to DoS attack

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-2280 PatchMethodFilter GET requires Consumes APPLICATION_JSON_PATCH_JSON

          • 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.
          • Resolved

          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) RESTEASY-2866 Ensure @Context-injected proxies implement all interfaces

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

          Web Link Analysis document

          Activity

            People

              rsigal@redhat.com Ronald Sigal
              jperkins-rhn James Perkins
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: