You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it an expected behaviour that resteasy reactive detects by default that method argument is path parameter and classic resteasy requires PathParam annotation for the same behaviour?
This is resteasy reactive version. This method requires only a path parameter for request:
@DELETE
@Path("/{id}")
fun removeById(id: UUID): SomeResponse {
}
And if I only change resteasy-reactive to classic resteasy this method also requires a body. If I want this method to require only a path parameter I need to add PathParam annotation:
@DELETE
@Path("/{id}")
fun removeById(@PathParam("id") id: UUID): SomeResponse {
}
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Is it an expected behaviour that resteasy reactive detects by default that method argument is path parameter and classic resteasy requires PathParam annotation for the same behaviour?
This is resteasy reactive version. This method requires only a path parameter for request:
And if I only change resteasy-reactive to classic resteasy this method also requires a body. If I want this method to require only a path parameter I need to add PathParam annotation:
Beta Was this translation helpful? Give feedback.
All reactions