[640][WFLY-19866] Add an analysis document for promoting the MicroPro… #641
Conversation
…file REST Client 4.0 API from preview to default. Signed-off-by: James R. Perkins <jperkins@redhat.com>
|
|
||
| === User Stories | ||
|
|
||
| A user wants to use the MicroProfile REST Client version 4.0 or use MicroProfile Platform 7.0. |
There was a problem hiding this comment.
Can you please elaborate how users can benefit from new features brought by new REST Client?
| from a stability level of `preview` to a stability level of `default`. | ||
|
|
||
| As you'll see in the release notes below, not much was added to the MicroProfile REST Client 4.0 API. There are only two | ||
| new methods added to the `RestClientBuilder` API. |
There was a problem hiding this comment.
https://microprofile.io/specifications/rest-client/4-0/
What about There was a clarification about closing the REST client when being injected via CDI? Is there some change in our implementation because of this?
There was a problem hiding this comment.
No, there is no change in our implementation for that. This was changed in resteasy-microprofile in resteasy/resteasy-microprofile#50. This issue arrived because of this fix.
| There would be no changes to security considerations for this upgrade. | ||
|
|
||
| [[test_plan]] | ||
| == Test Plan |
There was a problem hiding this comment.
@jamezp Can you please update this section based on the template?
There was a problem hiding this comment.
I'm not too sure what is needed TBH. We don't really have any tests in WildFly short of the TCK and other tests using the MP REST Client.
There is no subsystem configuration or anything. Do we want to add a bunch of tests? If we do, that might take some time.
…file REST Client 4.0 API from preview to default.
resolves #640