@@ -1359,7 +1359,7 @@ The following example has type and method level mappings:
1359
1359
==== URI patterns
1360
1360
[.small]#<<web-reactive.adoc#webflux-ann-requestmapping-uri-templates,Same as in Spring WebFlux>>#
1361
1361
1362
- You can map requests by using the following glob patterns and wildcards:
1362
+ You can map requests by using the following global patterns and wildcards:
1363
1363
1364
1364
* `?` matches one character
1365
1365
* `*` matches zero or more characters within a path segment
@@ -1439,10 +1439,10 @@ When multiple patterns match a URL, they must be compared to find the best match
1439
1439
by using `AntPathMatcher.getPatternComparator(String path)`, which looks for patterns that are more
1440
1440
specific.
1441
1441
1442
- A pattern is less specific if it has a lower count of URI variables and single wildcards
1443
- counted as 1 and double wildcards counted as 2. Given an equal score, the longer pattern is
1444
- chosen. Given the same score and length, the pattern with more URI variables than wildcards
1445
- is chosen.
1442
+ A pattern is less specific if it has a lower count of URI variables (counted as 1), single
1443
+ wildcards ( counted as 1), and double wildcards ( counted as 2) . Given an equal score, the
1444
+ longer pattern is chosen. Given the same score and length, the pattern with more URI variables
1445
+ than wildcards is chosen.
1446
1446
1447
1447
The default mapping pattern (`/{asterisk}{asterisk}`) is excluded from scoring and always
1448
1448
sorted last. Also, prefix patterns (such as `/public/{asterisk}{asterisk}`) are considered less
@@ -2291,7 +2291,7 @@ alternatively, set `@ModelAttribute(binding=false)`, as the following example sh
2291
2291
}
2292
2292
2293
2293
@PostMapping("update")
2294
- public String update(@Valid AccountUpdateForm form, BindingResult result,
2294
+ public String update(@Valid AccountForm form, BindingResult result,
2295
2295
@ModelAttribute(binding=false) Account account) { <1>
2296
2296
// ...
2297
2297
}
@@ -2300,7 +2300,7 @@ alternatively, set `@ModelAttribute(binding=false)`, as the following example sh
2300
2300
====
2301
2301
2302
2302
You can automatically apply validation after data binding by adding the
2303
- `javax.validation.Valid` annotation or Spring's `@Validated` annotation (ee
2303
+ `javax.validation.Valid` annotation or Spring's `@Validated` annotation (
2304
2304
<<core.adoc#validation-beanvalidation, Bean validation>> and
2305
2305
<<core.adoc#validation, Spring validation>>). The following example shows how to do so:
2306
2306
@@ -2458,7 +2458,7 @@ Java configuration keep this flag set to `false`, to maintain backwards compatib
2458
2458
However, for new applications, we recommend setting it to `true`.
2459
2459
2460
2460
Note that URI template variables from the present request are automatically made
2461
- available when expanding a redirect URL, and you need explicitly add them
2461
+ available when expanding a redirect URL, and you don't need to explicitly add them
2462
2462
through `Model` or `RedirectAttributes`. The following example shows how to define a redirect:
2463
2463
2464
2464
====
0 commit comments