Replace ParsingPathMatcher with PathPattern registry [SPR-15608]

[spring-projects-issues]

Brian Clozel opened SPR-15608 and commented

Now that PathPattern has been introduced, further changes can be applied to spring-webflux to simplify the routing algorithm.

Instead of relying on the ParsingPathMatcher and managing String instances, we could:

• AbstractHandlerMapping and subclasses should use PathPattern instances and a private registry instead of String and PathMatcher
• The PatternsRequestCondition should also keep an ordered collection of PathPattern and use a PathPatternParser, in order to replace String and PathMatcher

Other possible improvements:

• consider simplifying the various layer of caches (direct URLs, for example) and
• consider performance optimizations on the registry itself
• check defaults, see Review path matching options and defaults in the new path matching algorithms [SPR-14993] #19559

---

Issue Links:

• Review path matching options and defaults in the new path matching algorithms [SPR-14993] #19559 Review path matching options and defaults in the new path matching algorithms

Referenced from: commits 233c15b