Support access to all URI vars via @PathVariable Map
Issue: SPR-9289
This commit is contained in:
1
src/dist/changelog.txt
vendored
1
src/dist/changelog.txt
vendored
@@ -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)
|
||||
-------------------------------------
|
||||
|
||||
@@ -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<String, String></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
|
||||
|
||||
Reference in New Issue
Block a user