Add RESTEasy Configuration Attribute to jaxrs Subsystem

RESTEasy provides configuration parameters referred to as "context parameters". The context parameters can be set in various ways from system properties to Jakarta Servlet context parameters. Another way of setting these context parameters, is via the jaxrs subsystem.

The advantage of setting these in the jaxrs subsystem is the settings apply to all deployments unless explicitly overridden in the deployment. It also offers better validation of the values.

The following attribute should be added to the jaxrs subsystem:

This attribute will be added with its respective default. The value of the attribute will be used to set implicit servlet context parameters on each deployment. This will only be set if the context parameter was not already set as a servlet context parameter by the application being deployed.

There should be no backwards compatibility issues. This option is already available to be set via other means.

The implementation will be to simply add the new attribute to the subsystem. In a DeploymentUnitProcessor, which already exists, the attribute will be converted into a context property set in the servlet context parameters. The value from the subsystem will not overwrite values defined in the web.xml of the deployment being processed.

This will be a simple attribute that should not require any additional work for the admin clients.

There should be no impact on the security considerations here.

The attribute will have an integration test added as well as subsystem model tests. The testing framework to test the attribute already exists.

There is already documentation for the configuration option in the RESTEasy documentation. The attribute will have documentation in the management model and therefore in the model description available with the WildFly documentation. There will be no further documentation requirements needed.

A new attribute has been added to the jaxrs subsystem which was previously only available by configuring the context parameter at a deployment level. Configuring this at the subsystem level will apply it to all deployments, unless the deployment itself explicitly sets the parameter.