Spring/spring-framework
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Enable smart suffix pattern match for request mapping

Browse Source 
Following the introduction of ContentNegotiationManager that allows,
among other things, to configure the file extensions to use for content
negotiation, this change adds "smart" suffix pattern match that matches
against the configured file extensions only rather than against any
extension.

Given the request mapping "/jobs/{jobName}" and one configured file
extension ("json"), a request for "/jobs/my.job" will select the
pattern "/jobs/{jobName}" while a request for "/jobs/my.job.json" will
select the pattern "/jobs/{jobName}.json". Previously, both requests
would have resulted in the pattern "/jobs/{jobName}.*".

Issue: SPR-7632, SPR-8474
This commit is contained in:
Rossen Stoyanchev
2012-06-25 21:30:10 -04:00
parent f94aed8386
commit 4fd7645efd
7 changed files with 182 additions and 77 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
src/dist/changelog.txt vendored
View File

@@ -12,6 +12,7 @@ Changes in version 3.2 M2
* infer return type of parameterized factory methods (SPR-9493)
* add ContentNegotiationManager/ContentNegotiationStrategy to resolve requested media types
* add support for the HTTP PATCH method
* enable smart suffix pattern match in @RequestMapping methods (SPR-7632)
Changes in version 3.2 M1 (2012-05-28)
--------------------------------------