@@ -208,7 +208,7 @@ appropriate responses. By "`special beans`" we mean Spring-managed `Object` inst
208
208
implement framework contracts. Those usually come with built-in contracts, but
209
209
you can customize their properties and extend or replace them.
210
210
211
- The following table lists the special beans detected by the `DispatcherHandler `:
211
+ The following table lists the special beans detected by the `DispatcherServlet `:
212
212
213
213
[[mvc-webappctx-special-beans-tbl]]
214
214
[cols="1,2", options="header"]
@@ -1319,7 +1319,7 @@ The following example has type and method level mappings:
1319
1319
==== URI patterns
1320
1320
[.small]#<<web-reactive.adoc#webflux-ann-requestmapping-uri-templates,Same as in Spring WebFlux>>#
1321
1321
1322
- You can map requests by using the following glob patterns and wildcards:
1322
+ You can map requests by using the following global patterns and wildcards:
1323
1323
1324
1324
* `?` matches one character
1325
1325
* `*` matches zero or more characters within a path segment
@@ -1393,10 +1393,10 @@ When multiple patterns match a URL, they must be compared to find the best match
1393
1393
by using `AntPathMatcher.getPatternComparator(String path)`, which looks for patterns that are more
1394
1394
specific.
1395
1395
1396
- A pattern is less specific if it has a lower count of URI variables and single wildcards
1397
- counted as 1 and double wildcards counted as 2. Given an equal score, the longer pattern is
1398
- chosen. Given the same score and length, the pattern with more URI variables than wildcards
1399
- is chosen.
1396
+ A pattern is less specific if it has a lower count of URI variables (counted as 1), single
1397
+ wildcards ( counted as 1), and double wildcards ( counted as 2) . Given an equal score, the
1398
+ longer pattern is chosen. Given the same score and length, the pattern with more URI variables
1399
+ than wildcards is chosen.
1400
1400
1401
1401
The default mapping pattern (`/{asterisk}{asterisk}`) is excluded from scoring and always
1402
1402
sorted last. Also, prefix patterns (such as `/public/{asterisk}{asterisk}`) are considered less
@@ -2220,7 +2220,7 @@ alternatively, set `@ModelAttribute(binding=false)`, as the following example sh
2220
2220
}
2221
2221
2222
2222
@PostMapping("update")
2223
- public String update(@Valid AccountUpdateForm form, BindingResult result,
2223
+ public String update(@Valid AccountForm form, BindingResult result,
2224
2224
@ModelAttribute(binding=false) Account account) { <1>
2225
2225
// ...
2226
2226
}
@@ -2229,7 +2229,7 @@ alternatively, set `@ModelAttribute(binding=false)`, as the following example sh
2229
2229
2230
2230
2231
2231
You can automatically apply validation after data binding by adding the
2232
- `javax.validation.Valid` annotation or Spring's `@Validated` annotation (ee
2232
+ `javax.validation.Valid` annotation or Spring's `@Validated` annotation (
2233
2233
<<core.adoc#validation-beanvalidation, Bean validation>> and
2234
2234
<<core.adoc#validation, Spring validation>>). The following example shows how to do so:
2235
2235
@@ -2382,7 +2382,7 @@ Java configuration keep this flag set to `false`, to maintain backwards compatib
2382
2382
However, for new applications, we recommend setting it to `true`.
2383
2383
2384
2384
Note that URI template variables from the present request are automatically made
2385
- available when expanding a redirect URL, and you need explicitly add them
2385
+ available when expanding a redirect URL, and you don't need to explicitly add them
2386
2386
through `Model` or `RedirectAttributes`. The following example shows how to define a redirect:
2387
2387
2388
2388
[source,java,indent=0]
0 commit comments