Commit 912eb53d authored by Madhura Bhave's avatar Madhura Bhave

Clarify configuration class behavior based on bean conditions

parent b5221999
...@@ -6409,8 +6409,9 @@ on auto-configuration classes (since these are guaranteed to load after any user ...@@ -6409,8 +6409,9 @@ on auto-configuration classes (since these are guaranteed to load after any user
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`
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.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment