Consistent bean type checking for endpoint handlers [SPR-13725] #18298
Description
Juergen Hoeller opened SPR-13725 and commented
Our bean name iteration algorithms with bean type checks across messaging endpoints (AbstractMethodMessageHandler) and web endpoints (AbstractHandlerMethodMapping) are slightly inconsistent with respect to scoped target exclusion (#16173) and now also with respect to lenient treatment of unresolvable bean types (#17619). Let's fix this for 4.2.4, along the lines of the consistent method selection changes in 4.2.3 (#18230).
Affects: 4.2.3
Issue Links:
- EventListenerMethodProcessor resolves classes of lazy beans causing NoClassDefFoundError [SPR-13712] #17619 EventListenerMethodProcessor resolves classes of lazy beans causing NoClassDefFoundError
- Consistent method selection for listeners and endpoint mappings [SPR-13654] #18230 Consistent method selection for listeners and endpoint mappings
- MVC handler method detection should ignore scopedTarget.x in favor of corresponding proxy bean [SPR-11548] #16173 MVC handler method detection should ignore scopedTarget.x in favor of corresponding proxy bean
Referenced from: commits a0747c2