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

Minor fix in MVC reference doc chapter

Browse Source 
Issues: SPR-9111
This commit is contained in:
Rossen Stoyanchev
2012-02-12 19:54:17 -05:00
parent caa50a1d41
commit 997c6c56f7
1 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
spring-framework-reference/src/mvc.xml
View File

@@ -1575,16 +1575,18 @@ public void handle(@RequestBody String body, Writer writer) throws IOException {
&lt;bean id="castorMarshaller" class="org.springframework.oxm.castor.CastorMarshaller"/&gt;</programlisting>
<para>An <classname>@RequestBody</classname> method parameter can be
annotated with <classname>@Valid</classname>, in which case it will
annotated with <classname>@Valid</classname>, in which case it will be
validated using the configured <classname>Validator</classname>
instance. When using the MVC namespace a JSR-303 validator is
configured automatically assuming a JSR-303 implementation is
available on the classpath. If validation fails a
<classname>RequestBodyNotValidException</classname> is raised. The
exception is handled by the
<classname>DefaultHandlerExceptionResolver</classname> and results in
a <literal>400</literal> error sent back to the client along with a
message containing the validation errors.</para>
available on the classpath.</para>
<para>Unlike <classname>@ModelAttribute</classname> parameters, for which
a <classname>BindingResult</classname> can be used to examine the errors,
<classname>@RequestBody</classname> validation errors always result in a
<classname>MethodArgumentNotValidException</classname> being raised.
The exception is handled in the
<classname>DefaultHandlerExceptionResolver</classname>, which sends
a <literal>400</literal> error back to the client.</para>
<note>
<para>Also see <xref linkend="mvc-annotation-driven" /> for