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.

Sign up for GitHub

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

Jump to bottom

Order of interceptor calls is dependent on the way the interceptors are included [SWS-713] #806

Closed
gregturn opened this issue Jun 30, 2011 · 2 comments
Closed

Order of interceptor calls is dependent on the way the interceptors are included [SWS-713] #806

gregturn opened this issue Jun 30, 2011 · 2 comments
Assignees
@poutsma
Labels
in: core type: bug
Milestone
2.0.3

Comments

@gregturn
Copy link
Contributor

Jochen Terstiege opened SWS-713 and commented

The InterceptorsBeanDefinitionParser scans for interceptors in the following order: first "bean", then "ref", and so on. I.e. the order in which the interceptors are called is dependent on the way the interceptors are included.

One would expect that the interceptors are called in the order in which they were specified, so that changing a "bean" to a "ref" does not modify the calling order.

Affects: 2.0.2

Referenced from: commits 9f9e06d

1 votes, 1 watchers
@gregturn
Copy link
Contributor Author

gregturn commented Oct 6, 2011

Arjen Poutsma commented

Fixed in SVN. Let me know if it works for you.

@gregturn
Copy link
Contributor Author

gregturn commented May 4, 2012

Arjen Poutsma commented

Closing old issues

@gregturn gregturn closed this as completed May 4, 2012
@gregturn gregturn added this to the 2.0.3 milestone Sep 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@poutsma poutsma

Labels
in: core type: bug
Projects
None yet
Milestone
2.0.3
Development

No branches or pull requests
2 participants
@gregturn @poutsma