Merge pull request #16166 from viktoriya-kutsarova

* pr/16166:
  Polish "Update ambiguous documentation about ConfigurationProperties"
  Update ambiguous documentation about ConfigurationProperties
pull/16247/head
Stephane Nicoll 6 years ago
commit d77f69cfa9

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

Loading…
Cancel
Save