Support access to all URI vars via @PathVariable Map

Issue: SPR-9289
This commit is contained in:
Rossen Stoyanchev
2012-05-14 16:01:16 -04:00
parent 698d004260
commit 1d0e484eac
8 changed files with 256 additions and 48 deletions

View File

@@ -22,6 +22,7 @@ Changes in version 3.2 M1
* fix content negotiation issue when sorting selected media types by quality value
* Prevent further writing to the response when @ResponseStatus contains a reason
* Deprecate HttpStatus codes 419, 420, 421
* support access to all URI vars via @PathVariable Map<String, String>
Changes in version 3.1.1 (2012-02-16)
-------------------------------------

View File

@@ -992,6 +992,11 @@ public String findPet(<emphasis role="bold">@PathVariable</emphasis> String owne
return "displayPet";
}</programlisting>
<para>When a <interfacename>@PathVariable</interfacename> annotation is
used on a <classname>Map&lt;String, String&gt;</classname> argument, the
map is populated with all URI template variables.
</para>
<para>A URI template can be assembled from type and path level
<emphasis>@RequestMapping</emphasis> annotations. As a result the
<methodname>findPet()</methodname> method can be invoked with a URL