-
Notifications
You must be signed in to change notification settings - Fork 38.5k
Inconsistent interpretation of parameter annotations in interface-based handler methods [SPR-14021] #18593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Greg Turnquist commented Moved to Spring Framework since this involves Spring MVC. |
Paul commented I'm sorry, didn't know where to post it to. |
Rossen Stoyanchev commented Annotations on method parameters are expected to be in the implementing class. I'm not sure why |
Paul commented Now, when Spring Cloud project exists — it's good idea to have single interface for endpoint and FeignClient, because client is declarative and is being build depending on annotations. |
Paul commented Reproduce tests in pull request: spring-attic/spring-framework-issues#120 |
Rossen Stoyanchev commented Sorry for not seeing this right away but |
Rossen Stoyanchev commented Resolving as duplicate of #15682. |
Paul opened SPR-14021 and commented
If I have Spring MVC interface with methods, whose params are annotated with different param types like this:
and class, which is derived from this interface, but arguments of methods are not annotated with Param annotations mapper behaviour is inconsistent:
values, annotated with
@RequestParam
get their values in implementing class, and with@PathVariable
— not.Issue Links:
Referenced from: commits spring-attic/spring-framework-issues@bfbb943, spring-attic/spring-framework-issues@de6f178
The text was updated successfully, but these errors were encountered: