Document ConfigFile...Initializer limitations
Update the reference documentation with a note about the limitations of ConfigFileApplicationContextInitializer. Fixes gh-6120
This commit is contained in:
parent
7b641d5d55
commit
51ede0cac6
|
@ -5370,6 +5370,12 @@ this when you don't need the full features provided by `@SpringBootTest`.
|
||||||
initializers = ConfigFileApplicationContextInitializer.class)
|
initializers = ConfigFileApplicationContextInitializer.class)
|
||||||
----
|
----
|
||||||
|
|
||||||
|
NOTE: Using `ConfigFileApplicationContextInitializer` alone won't provide support for
|
||||||
|
`@Value("${...}")` injection. Its only job is to ensure that `application.properties` files
|
||||||
|
are loaded into Spring's `Environment`. For `@Value` support you need to either
|
||||||
|
additionally configure a `PropertySourcesPlaceholderConfigurer` or use `@SpringBootTest`
|
||||||
|
where one will be auto-configured for you.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
[[boot-features-environment-test-utilities]]
|
[[boot-features-environment-test-utilities]]
|
||||||
|
|
Loading…
Reference in New Issue