Skip to content

Conversation

YongGoose
Copy link

Prior to this change, if the default CGLIB proxy creation failed for a non-subclassable target class (e.g., due to a private constructor), the ApplicationContext would fail to start.

fixes #31634

Prior to this change, if the default CGLIB proxy creation failed for a
non-subclassable target class (e.g., due to a private constructor), the
ApplicationContext would fail to start.

Signed-off-by: yongjunhong <yongjunh@apache.org>
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Aug 19, 2025
@sbrannen sbrannen added in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement labels Aug 19, 2025
@YongGoose
Copy link
Author

@sbrannen
I think this feature could be helpful for the Spring Framework.
Could you give me some feedback on it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: waiting-for-triage An issue we've not yet triaged or decided on type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fall back from cglib to JDK proxies when possible
3 participants