Improve property placeholder resolution when multiple configurers are declared [SPR-10654] #15282
Labels
in: core
Issues in core modules (aop, beans, core, context, expression)
status: duplicate
A duplicate of another issue
type: enhancement
A general enhancement
Bozhidar Bozhanov opened SPR-10654 and commented
There are some problems when working with multiple <context:property-placeholder /> are defined (possibly in multiple .xml files)
when there are more than one configurers, the "ignore-unresolved" must be set to "true", otherwise startup fails, because one configurer doesn't have all the required properties
if there are nested properties obtained from multiple locations, startup fails, because ignore-unresolved does not affect the ignoreUnresolvableNestedPlaceholders property.
Here are some more details on my current issue: http://stackoverflow.com/questions/17084563/spring-namespacehandler-and-multiple-property-placeholders
Currently it is solved by setting env.setIgnoreUnresolvableNestedPlaceholders(true), but I think there should be available for configuration via tha *PlaceholderConfigurer. Currently it is a property of the PropertyResolver and is not accessible from anywhere, apart from the Environment
Affects: 3.2 GA
Issue Links:
PropertyPlaceholderConfigurer
s [SPR-9989] #14623 Using multiple PropertyPlaceholderConfigurer breaks@Value
default value behavior ("duplicates")The text was updated successfully, but these errors were encountered: