The following context parameters should be added as configuration parameters to the jaxrs subsystem:

• RESTEASY-2646 resteasy.match.cache.enabled: Defaults to true and can be disabled to no longer cache resource requests to the same URL.
• RESTEASY-2646 resteasy.match.cache.size : Defaults to 2048 and when the cache is enabled, changes the size limit for the cache.
• [RESTEASY-2782] resteasy.original.webapplicationexception.behavior : Defaults to false. Set to tru", this parameter will restore the original behavior in which a Client running in a resource method will throw a Jakarta RESTful Web Services WebApplicationException instead of a RESTEasy version with a sanitized Response. Further documentation can be found at https://docs.resteasy.dev/6.2/userguide/#_resteasywebapplicationexception

Previously resteasy.proxy.implement.all.interfaces was included in this list. It defaults to false. This seems related to RESTEASY-2866. Looking at the comments, I wonder how useful this is to WildFly and EAP. The `@Context` support is being deprecated in Jakarta REST in favor of CDI. I don't have a strong preference either way, but I'm inclined to leave this off as it may be deprecated in the not so near future.

Previously resteasy.patch.filter.legacy was also included, see RESTEASY-2849. However, this should likely be deprecated. If using Jackson, use Jackson for patching. If using Jakarta JSON Binding, use Jakarta JSON Binding for patching. This would be a change in RESTEasy itself. I've filed RESTEASY-3660 for this.

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.