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
We're explicitly excluding Collection and Map beans from fallback matching now. They are being treated specifically for autowiring purposes in general, so it's not out of the ordinary to handle them specifically here as well.
However, this also means that Collection and Map beans never match unless they qualify as a full generic type match. This is easy enough to accomplish with factory methods with a specifically declared return type... but hard with a regular XML bean definition. I'm not too concerned though since this feature is not primarily about plain value holder collections; it's rather about implementations beans which happen to implement Collection / Map as well. Arbitrary Collection and Map beans can still be injected using @Resource, as before.
Phil Webb opened SPR-13963 and commented
Upgrading Spring Boot to Framework to 4.3is not currently possible due to failure in
EndpointAutoConfigurationTests
.It appears that this line in
EndpointAutoConfiguration
:No longer works correctly as String values end up in the map.
I believe that commit 3f74a74481d is ultimately responsible as rolling this back seems to fix the issue.
Affects: 4.3 RC1
Issue Links:
Referenced from: commits 48ee9b5, 1b53edf
The text was updated successfully, but these errors were encountered: