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
{{ message }}
This repository was archived by the owner on Apr 4, 2025. It is now read-only.
It would be beneficial if @Configuration classes that are intended to be sub-classed by users could be annotated with @Configuration(proxyBeanMethods=false) to indicate that they do not require proxying. If there are configuration classes where proxying is required (due to inter-dependent @Bean methods) it would be beneficial if they were reworked so that proxying is no longer required.
The text was updated successfully, but these errors were encountered:
wilkinsona
changed the title
Rework @Configuration class that users may subclass to indicate whether or not they required proxying
Rework @Configuration class that users may subclass to indicate whether or not they require proxying
Mar 12, 2019
This is related to spring-projects/spring-session#1345.
It would be beneficial if
@Configuration
classes that are intended to be sub-classed by users could be annotated with@Configuration(proxyBeanMethods=false)
to indicate that they do not require proxying. If there are configuration classes where proxying is required (due to inter-dependent@Bean
methods) it would be beneficial if they were reworked so that proxying is no longer required.The text was updated successfully, but these errors were encountered: