Support to Create a Proxy From an Annotated HTTP Service Interface #28386
Assignees
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: enhancement
A general enhancement
Milestone
Comments
rstoyanchev
added
in: web
rstoyanchev
added a commit
that referenced
this issue
Apr 27, 2022
rstoyanchev
pushed a commit
that referenced
this issue
Apr 27, 2022
rstoyanchev
added a commit
that referenced
this issue
Apr 27, 2022
rstoyanchev
added a commit
that referenced
this issue
Apr 27, 2022
rstoyanchev
added a commit
that referenced
this issue
Apr 27, 2022
HttpRequestValues is immutable and exposes a builder. See gh-28386
rstoyanchev
added a commit
that referenced
this issue
Apr 27, 2022
rstoyanchev
added a commit
that referenced
this issue
Apr 27, 2022
rstoyanchev
added a commit
that referenced
this issue
Apr 27, 2022
Boolean return value indicates if the value was resolved or not. See gh-28386
rstoyanchev
added a commit
that referenced
this issue
May 3, 2022
rstoyanchev
added a commit
that referenced
this issue
May 3, 2022
Extract NamedValueArgumentResolverTests. Move form data vs query params tests into HttpRequestValues. See gh-28386
rstoyanchev
added a commit
that referenced
this issue
May 3, 2022
Support for RequestBody arguments. List supported arguments on HttpExchange. Improve null handling. See gh-28386
jhoeller
added a commit
that referenced
this issue
May 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This has been raised before, see #16747 and related (duplicate) issues, but was done under Spring Cloud instead, first as an OpenFeign integration and more recently as a Retrofit integration.
The goal for this issue is first class support in the Spring Framework to create a client proxy from an annotated, HTTP service interface, since it is more generally applicable. Spring Cloud can then provide additional features around that. The same is also planned for RSocket with #24456.
Methods on such an HTTP service interface will support many of the same method arguments as for server side handling with
@RequestMappingmethods, but narrowing the choice down to those arguments that apply to both client and server side use. On the client side, argument values are used to populate the request, while on the server side, argument values are extracted from the request.Methods of the HTTP service interface will require a new annotation, similar in purpose to
@RequestMapping, but to declare an HTTP exchange in a way that is neutral to client or server perspective.The text was updated successfully, but these errors were encountered: