|
35 | 35 | * <p>Classes with {@code @ControllerAdvice} can be declared explicitly as Spring
|
36 | 36 | * beans or auto-detected via classpath scanning. All such beans are sorted via
|
37 | 37 | * {@link org.springframework.core.annotation.AnnotationAwareOrderComparator
|
38 |
| - * AnnotationAwareOrderComparator}, i.e. based on |
| 38 | + * AnnotationAwareOrderComparator}, based on |
39 | 39 | * {@link org.springframework.core.annotation.Order @Order} and
|
40 | 40 | * {@link org.springframework.core.Ordered Ordered}, and applied in that order
|
41 | 41 | * at runtime. For handling exceptions, an {@code @ExceptionHandler} will be
|
|
51 | 51 | * root exception mappings on a prioritized advice bean with a corresponding order.
|
52 | 52 | *
|
53 | 53 | * <p>By default, the methods in an {@code @ControllerAdvice} apply globally to
|
54 |
| - * all controllers. Use selectors {@link #annotations}, |
| 54 | + * all controllers. Use selectors such as {@link #annotations}, |
55 | 55 | * {@link #basePackageClasses}, and {@link #basePackages} (or its alias
|
56 | 56 | * {@link #value}) to define a more narrow subset of targeted controllers.
|
57 | 57 | * If multiple selectors are declared, boolean {@code OR} logic is applied, meaning
|
58 | 58 | * selected controllers should match at least one selector. Note that selector checks
|
59 |
| - * are performed at runtime and so adding many selectors may negatively impact |
| 59 | + * are performed at runtime, so adding many selectors may negatively impact |
60 | 60 | * performance and add complexity.
|
61 | 61 | *
|
62 | 62 | * @author Rossen Stoyanchev
|
|
0 commit comments