[
https://issues.redhat.com/browse/WFLY-12779?page=com.atlassian.jira.plugi...
]
Ronald Sigal commented on WFLY-12779:
-------------------------------------
I've created a pull request (
https://github.com/resteasy/Resteasy/pull/2250) with the
necessary changes to RESTEasy for release 3.10.0.Final.
One thing I would like to reconsider is the proposal to implement the parameter
"resteasy.config.resteasy.parameters.only". Thinking more about it, it seems
awkward to restrict the scope of *some* ConfigSources when most of them, the default
ConfigSources as well as those added in Wildfly, are out of RESTEasy's control.
I'm thinking now that it makes more sense to allow any parameters to be retrieved in
RESTEasy.
Incorporate MicroProfile Config in RESTEasy
-------------------------------------------
Key: WFLY-12779
URL:
https://issues.redhat.com/browse/WFLY-12779
Project: WildFly
Issue Type: Feature Request
Reporter: Ronald Sigal
Assignee: Ronald Sigal
Priority: Major
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.
In RESTEasy 4.x, all parameters, both RESTEasy parameters and application parameters, are
available from all ConfigSources to both RESTEasy and application code. In RESTEasy 3.x,
we propose to add a RESTEasy parameter,
"resteasy.config.resteasy.parameters.only", which, when set to "true",
will limit the three RESTEasy ConfigSources to returning RESTEasy parameters only. It will
default to "true".
--
This message was sent by Atlassian Jira
(v7.13.8#713008)