Add option to wrap return type in a generic class #295
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JAX RS code generator actully doesn't take into consideration response status. The problem is that if the methods of API's interface return POJO, the assumed response code is 200. To define alternative status, either all the methods would have to return
jakarta.ws.rs.Responsewhich is not very useful or the impelemntation of JAX RS has a generic class which represents response with option to specify status or headers. In RestEasy such class isorg.jboss.resteasy.reactive.RestResponse.This PR is adding configuration to define such generic class name to use it instead of model class directly.