|
|
@ -7639,8 +7639,9 @@ on auto-configuration classes (since these are guaranteed to load after any user
|
|
|
|
bean definitions have been added).
|
|
|
|
bean definitions have been added).
|
|
|
|
|
|
|
|
|
|
|
|
NOTE: `@ConditionalOnBean` and `@ConditionalOnMissingBean` do not prevent `@Configuration`
|
|
|
|
NOTE: `@ConditionalOnBean` and `@ConditionalOnMissingBean` do not prevent `@Configuration`
|
|
|
|
classes from being created. Using these conditions at the class level is equivalent to
|
|
|
|
classes from being created. The only difference between using these conditions at the class level
|
|
|
|
marking each contained `@Bean` method with the annotation.
|
|
|
|
and marking each contained `@Bean` method with the annotation is that the former prevents
|
|
|
|
|
|
|
|
registration of the `@Configuration` class as a bean if the condition does not match.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|