Update ambiguous documentation about ConfigurationProperties

See gh-16166
This commit is contained in:
Viktoriya Kutsarova 2019-03-07 17:17:22 +01:00 committed by Stephane Nicoll
parent 015de55f58
commit 6b6ac28430
1 changed files with 5 additions and 4 deletions

View File

@ -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]
----