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
I think this is a reasonable backport candidate as with Spring Data we don't want to force users on to 3.2 abruptly and the logs for the overridden bean definitions might lead users into thinking they're setting up their application context invalidly. Furthermore, even if the duplicate invocation doesn't cause any issues with our ImportBeanDefinitionRegistrar it will for implementations which use auto-generated bean names as they'll accidentally register two bean instances which might break autowiring by type as no unique bean then can be found.
Maybe worth mentioning that I am perfectly fine for this one not making it into 3.1.3. I just think it's important to have in the 3.1.x timeline before we officially declare it as done.
Oliver Drotbohm opened SPR-9939 and commented
I think this is a reasonable backport candidate as with Spring Data we don't want to force users on to 3.2 abruptly and the logs for the overridden bean definitions might lead users into thinking they're setting up their application context invalidly. Furthermore, even if the duplicate invocation doesn't cause any issues with our
ImportBeanDefinitionRegistrar
it will for implementations which use auto-generated bean names as they'll accidentally register two bean instances which might break autowiring by type as no unique bean then can be found.This issue is a backport sub-task of #14558
Issue Links:
@Enable
registrars invoked with subclass for annotation placed on superclass (3.2.x)Referenced from: commits spring-projects/spring-hateoas@48b039a, spring-projects/spring-hateoas@3976ae1
The text was updated successfully, but these errors were encountered: