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

Make use of Servlet 4.0 mapping introspection when available [SPR-15320] #19883

Closed
spring-projects-issues opened this issue Mar 6, 2017 · 1 comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) status: superseded An issue that has been superseded by another type: enhancement A general enhancement

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented Mar 6, 2017

Juergen Hoeller opened SPR-15320 and commented

Servlet 4.0 b03 is available now, introducing support for HttpServletRequest.getServletMapping(). As discussed, let's research what we can transparently infer from this when available at runtime, as an alternative to "guessing" about Servlet-level URL mappings in UrlPathHelper. If there isn't any distinct advantage, we can also keep our path-based code as it is, but we should make up our mind in time for 5.0 RC1 here.


Issue Links:

@rstoyanchev
Copy link
Contributor

This is superseded by #25100.

@rstoyanchev rstoyanchev added the status: superseded An issue that has been superseded by another label Jun 26, 2020
@rstoyanchev rstoyanchev removed this from the 5.x Backlog milestone Jun 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) status: superseded An issue that has been superseded by another type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants