Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify configuration class behavior based on bean conditions

Browse Source
This commit is contained in:
Madhura Bhave
2018-07-17 16:34:01 -07:00
parent b522199920
commit 912eb53d7a
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc
View File

@@ -6409,8 +6409,9 @@ on auto-configuration classes (since these are guaranteed to load after any user
beans definitions have been added).
NOTE: `@ConditionalOnBean` and `@ConditionalOnMissingBean` do not prevent `@Configuration`
classes from being created. Using these conditions at the class level is equivalent to
marking each contained `@Bean` method with the annotation.
classes from being created. The only difference between using these conditions at the class level
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.