Open
Description
In Spring MVC it is possible to annotate body parameter as optional using @RequestBody(required = false)
parameter annotation, e.g.:
@FeignClient("foo-service")
public interface FooService {
@RequestMapping(value = "/foo", method = RequestMethod.POST)
void doFoo(@RequestBody(required = false) FilterDto filter);
}
However, Spring-Feign contract does not consider the optionality flag which leads to an IllegalStateException on proxy bootstrapping in consumer when calling something like:
fooService.doFoo(null);
java.lang.IllegalArgumentException: Body parameter 0 was null
at feign.Util.checkArgument(Util.java:102)
at feign.ReflectiveFeign$BuildEncodedTemplateFromArgs.resolve(ReflectiveFeign.java:323)
at feign.ReflectiveFeign$BuildTemplateByResolvingArgs.create(ReflectiveFeign.java:213)
at feign.SynchronousMethodHandler.invoke(SynchronousMethodHandler.java:72)
at feign.ReflectiveFeign$FeignInvocationHandler.invoke(ReflectiveFeign.java:103)
It is expected that null
can be passed as parameter since it is optional.
Using:
- spring-cloud-starter-feign:1.1.0.RELEASE
- feign-core:8.16.2
Activity
daniellavoie commentedon May 29, 2016
From the stack trace you should understand that this issue is a pure Feign problem. Spring Cloud Netflix facilitate Netflix OSS component integration into Spring. I would suggest you to open an issue on the feign project.
dimw commentedon May 30, 2016
@daniellavoie, thanks for your feedback. Indeed, initially I was about to open this issue on the Feign project (because of the reasons admitted by you) but stack traces should not be always interpreted literally. Basically it seems not like a "a pure Feign problem" for me. Please correct me if I am wrong but:
@RequestBody
annotation and translate therequired
flag to Feign metadata.@RequestBody
) so even it can see the annotations provided on the method, it cannot (and should not) understand semantics of these.In fact, there might be currently no way in Feign to handle optional request bodies. However, this behavior should be at least documented in this project (because of the difference to behavior anticipated in Spring MVC). Further, it might be considered to create a certain RequestBodyParameterProcessor which catches the issue one level higher before letting Feign to throw semi-reasonable exception.
daniellavoie commentedon May 30, 2016
You are right. Looks like I had a bad understanding of Spring Cloud Feign. I'll try to have a look and see if I can come up with a trick to handle an optinal parameter. If you have any inspiration, feel free to give some help ;)
dimw commentedon Jun 5, 2016
@spencergibb: Do you think you can drop a line and explain why this issue has been closed without any further comment?
spencergibb commentedon Jun 8, 2016
Sorry about that, it was a mistake.
[-]Optional request body should be supported[/-][+]Optional request body should be supported by feign[/+]realdammy commentedon May 11, 2017
Hello @spencergibb, any update on this issues?
ryanjbaxter commentedon May 11, 2017
@realdammy it is labeled as an enhancement but as far as I know no one is working on it at the moment. If you want to submit a PR for it that would be more than welcome.
dyc87112 commentedon Aug 17, 2017
@ryanjbaxter I try to fix this issue. But feign always check the body, so I have to wait this PR : OpenFeign/feign#583.
If this PR can be accept. I will create another PR for here.
@dimw Thanks for your analysis.
sdhery commentedon Nov 25, 2017
Already have a solution?
dyc87112 commentedon Nov 27, 2017
@sdhery OpenFeign/feign#583 has not been accept,so you need compile feign by yourself,then write an
RequestBodyParameterProcessor
implementsAnnotatedParameterProcessor
interface to support this issue