|
|
|
@ -6252,7 +6252,7 @@ In the example above, the `myService` bean is going to be created if no bean of |
|
|
|
TIP: You need to be very careful about the order that bean definitions are added as these |
|
|
|
TIP: You need to be very careful about the order that bean definitions are added as these |
|
|
|
conditions are evaluated based on what has been processed so far. For this reason, |
|
|
|
conditions are evaluated based on what has been processed so far. For this reason, |
|
|
|
we recommend only using `@ConditionalOnBean` and `@ConditionalOnMissingBean` annotations |
|
|
|
we recommend only using `@ConditionalOnBean` and `@ConditionalOnMissingBean` annotations |
|
|
|
on auto-configuration classes (since these are guaranteed to load after any user-define |
|
|
|
on auto-configuration classes (since these are guaranteed to load after any user-defined |
|
|
|
beans definitions have been added). |
|
|
|
beans definitions have been added). |
|
|
|
|
|
|
|
|
|
|
|
NOTE: `@ConditionalOnBean` and `@ConditionalOnMissingBean` do not prevent `@Configuration` |
|
|
|
NOTE: `@ConditionalOnBean` and `@ConditionalOnMissingBean` do not prevent `@Configuration` |
|
|
|
|