You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My case is:
In the file classpath:options.properties property filemongo.slaveOk is not set.
In the file ${user.home}/.app/options.properties property is set to true.
Spring is resolving property to value false. It is using default setting if the first location of property files does not contains it.
I have debugged this case once again and I have found that I have a problem because I am using a few PropertySourcesPlaceholderConfigurer objects (each for the specific domain)
When I started using default value using : notation, the first one if does not find property in each files subset it is inserting default value in it.
When having many PropertySourcesPlaceholderConfigurert hen the last PropertySourcesPlaceholderConfigurer should set default value.
Andrzej Wisłowski opened SPR-10619 and commented
When using property files configuration like this:
and setting property value to the spring component:
I got invalid property resolved.
My case is:
In the file
classpath:options.properties property filemongo.slaveOk
is not set.In the file
${user.home}/.app/options.properties
property is set to true.Spring is resolving property to value false. It is using default setting if the first location of property files does not contains it.
Affects: 3.2 GA
Issue Links:
PropertyPlaceholderConfigurer
s [SPR-9989] #14623 Using multiple PropertyPlaceholderConfigurer breaks@Value
default value behavior ("duplicates")Referenced from: commits d7ec20a
The text was updated successfully, but these errors were encountered: