Update documentation with regards to differences between @MVC 3.0/3.1
Although the reference documentation listed the new @MVC support classes and their benefits, it did not explicitly mention a few use cases that are no longer supported. There is now a specific section on the new support classes listing exactly what is not supported. Similary the @RequestMapping annotation never refered explicitly to the existence of old and new support and never made it clear exactly what the differences are. Both have not been corrected. SPR-9063, SPR-9042
This commit is contained in:
@@ -38,7 +38,7 @@ Changes in version 3.1.1 (2012-02-13)
|
||||
* added property to RedirectView to disable expanding URI variables in redirect URL
|
||||
* fixed request mapping bug involving direct vs pattern path matches with HTTP methods
|
||||
* removed check for HTTP "POST" when resolving multipart request controller method arguments
|
||||
|
||||
* update @RequestMapping and reference docs wrt differences between @MVC 3.1 and @MVC 2.5-3.0
|
||||
|
||||
Changes in version 3.1 GA (2011-12-12)
|
||||
--------------------------------------
|
||||
|
||||
Reference in New Issue
Block a user