Skip to content

Consolidate support for HandlerInterceptor and MappedInterceptor types in AbstractHandlerMapping [SPR-8352] #12999

@spring-projects-issues

Description

@spring-projects-issues

Rossen Stoyanchev opened SPR-8352 and commented

MappedInterceptors are dealt with in AbstractUrlHandlerMapping as opposed to in its base class AbstractHandlerMapping because MappedInterceptors require access to a UrlPathHelper and a PathMatcher. This worked initially but the newly introduced AbstractHandlerMethodMapping extends directly from AbstractUrlHandlerMapping and there may be other such implementations (e.g. FlowUrlHandlerMapping).

The goal of this ticket is to consolidate handling of HandlerInterceptors and MappedInterceptors, provide a single setter for configuring both, and apply them to requests in a way that is re-usable across sub-classes of AbstractHandlerMapping.


Affects: 3.1 M1

Issue Links:

Metadata

Metadata

Assignees

Labels

in: webIssues in web modules (web, webmvc, webflux, websocket)type: enhancementA general enhancement

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions