Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

About the change in the advice order in Spring AOP #28882

Closed
zhujiuchao opened this issue Jul 28, 2022 · 2 comments
Closed

About the change in the advice order in Spring AOP #28882

zhujiuchao opened this issue Jul 28, 2022 · 2 comments
Labels
in: core Issues in core modules (aop, beans, core, context, expression) status: invalid An issue that we don't feel is valid

Comments

@zhujiuchao
Copy link

I created a Maven project to test the AOP notification order, but I find that when the version of Spring-context in the pom. xml file is 5.2.13-RELEASE and 5.2.5-RELEASE, I get different results. I wonder if this is a bug or if it was intentionally changed.  What if it was intentionally changed?  Could you please tell me the reason? Please check the attached picture
issue picture

aoptestone.zip

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Jul 28, 2022
@weixiaobaoL
Copy link

It's because #25186 for support declared method of the java7 not matched the source code.

@sbrannen sbrannen added status: invalid An issue that we don't feel is valid in: core Issues in core modules (aop, beans, core, context, expression) and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Jan 6, 2023
@sbrannen
Copy link
Member

sbrannen commented Jan 6, 2023

As @weixiaobaoL pointed out, this change in behavior was intentional.

See:

In light of that I am closing this issue.

@sbrannen sbrannen closed this as not planned Won't fix, can't repro, duplicate, stale Jan 6, 2023
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: invalid An issue that we don't feel is valid
Projects
None yet
Development

No branches or pull requests

4 participants