Skip to content
This repository was archived by the owner on Apr 4, 2025. It is now read-only.

Rework @Configuration class that users may subclass to indicate whether or not they require proxying #60

Closed
wilkinsona opened this issue Mar 12, 2019 · 1 comment
Milestone

Comments

@wilkinsona
Copy link
Member

wilkinsona commented 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.

@wilkinsona 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
@gregturn
Copy link
Contributor

Thanks @wilkinsona. When we upgrade to Spring Framework 5.2, we'll be able to consider it.

@gregturn gregturn added this to the 2.2.0.RC2 milestone Sep 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants