You know I can't find that sendRequest() code in the Framework. Looks like your own custom code. And then it isn't clear why just don't check for the AbstractIntegrationMessageBuilder as well and don't call its build() if you need.
The idea behind returning a AbstractIntegrationMessageBuilder now is to pursue some optimization on the AbstractMessageProducingHandler when we build an output message.
This is not a bug on the Framework level and has been done deliberately as a breaking change and that's why it made it into the major project revision - 5.0.
So, if you do your own code like that, very tied to the Framework internal logic, you just need to follow it and handle all the possible cases.
See AbstractMessageProducingHandler for more info:
Alex Khimach opened INT-4426 and commented
In spring-integration-http-5.0.*.RELEASE.jar method:
This cause "Unknown response type exception". result should have "Message" type but it had "MessageBuilder" type:
The text was updated successfully, but these errors were encountered: