-
Notifications
You must be signed in to change notification settings - Fork 38.5k
Provide access to all configured interceptors in AbstractHandlerMapping #28985
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
Comments
Please, elaborate on your reason for this request. Generally, the interceptors are configured and invoked within the |
I'm implementing our development framework based on Springboot, and since we have hundreds of business function developers, and we maintain hundreds of systems, and their Java development capabilities are high and low, I have to collect information while the program is running and automatically analyze the differences in changes in production materials. So I used a unified main class in the framework, called the start method of applicationContext in the main method, and then triggered the information collection operation in the start event, and the collected information will be written to a json file. Here's some of my sample code:
|
Of course, we not only collected the information involved in the above sample code, but also collected other information. My english translated by bing |
Thanks for the feedback. We do expose all interceptors on |
Thank you! yes I need the public method for collected the interceptor list。 |
We can't have a public Instead I promoted the existing |
Versions
Spring Version 5.3.22
Overview
I wanted to get all the HandlerInterceptor that had been registered in Spring MVC after the application was successfully launched, but I found that this method was protected, so it could not be obtained directly, and I had to use the reflection method to call, so it was recommended to set it to a public method.
My code was:
I also suggest that Springboot's actuator provide endpoints to get that information。
The text was updated successfully, but these errors were encountered: