Browse Source

Update ambiguous documentation about ConfigurationProperties

See gh-16166
pull/16247/head
Viktoriya Kutsarova 7 years ago committed by Stephane Nicoll
parent
commit
6b6ac28430
  1. 9
      spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc

9
spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc

@ -978,13 +978,14 @@ name of the bean is used. @@ -978,13 +978,14 @@ name of the bean is used.
The bean name in the example above is `acme-com.example.AcmeProperties`.
====
Even if the preceding configuration creates a regular bean for `AcmeProperties`, we
The preceding configuration creates a regular bean for `AcmeProperties`. We
recommend that `@ConfigurationProperties` only deal with the environment and, in
particular, does not inject other beans from the context. Having said that, the
particular, does not inject other beans from the context. Keep in mind that the
`@EnableConfigurationProperties` annotation is _also_ automatically applied to your
project so that any _existing_ bean annotated with `@ConfigurationProperties` is
configured from the `Environment`. You could shortcut `MyConfiguration` by making sure
`AcmeProperties` is already a bean, as shown in the following example:
configured from the `Environment`. Instead of annotating `MyConfiguration` with
`@EnableConfigurationProperties(AcmeProperties.class)`, you could make `AcmeProperties`
a bean, as shown in the following example:
[source,java,indent=0]
----

Loading…
Cancel
Save