improve performance of getHandlerInternal #29589
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In some scenarios, we need to get
HandlerMethod
ahead of org.springframework.web.reactive.DispatcherHandler, such as an implement of authentication by WebFilterHandlerMethod
is necessary but there is no alternative way to get it withon WebFilter, which limited the capabilities of WebFilter. so, we need callgetHandler
, however this may lead to repeated call of lookupHandlerMethod as issue:spring-framework/spring-webflux/src/main/java/org/springframework/web/reactive/result/method/AbstractHandlerMethodMapping.java
Line 293 in 00da70e
To avoid duplicate search for
HandlerMethod
inmapping.getHandler
, I suggest implementing a improved getHandlerInternal, in whichHandlerMethod
would be searched in attributes at first.related issue:#29591