org.springframework.beans.factory.config Documentation Differences

This file contains all the changes in documentation in the package org.springframework.beans.factory.config as colored differences. Deletions are shown like this, and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

Abstract base class for property resource configurers that resolve placeholders in bean definition property values. Implementations pull values from a properties file or other org.springframework.core.env.PropertySource property source into bean definitions.

The default placeholder syntax follows the Ant / Log4J / JSP EL style:

${...}

Example XML bean definition:

{@code

    
    

}

Example properties file:

 driver=com.mysql.jdbc.Driver
 dbname=mysql:mydb

Annotated bean definitions may take advantage of property replacement using the @Value annotation:

@Value("${person.age}")

Implementations check simple property values, lists, maps, props, and bean names in bean references. Furthermore, placeholder values can also cross-reference other placeholders, like:

rootPath=myrootdir
subPath=${rootPath}/subdir

In contrast to PropertyOverrideConfigurer, subclasses of this type allow filling in of explicit placeholders in bean definitions.

If a configurer cannot resolve a placeholder, a BeanDefinitionStoreException will be thrown. If you want to check against multiple properties files, specify multiple resources via the locations property. You can also define multiple configurers, each with its own placeholder syntax. Use .ignoreUnresolvablePlaceholders to intentionally suppress throwing an exception if a placeholder cannot be resolved.

Default property values can be defined globally for each configurer instance via the properties property, or on a property-by-property basis using the default value separator which is {@code ":"} by default and customizable via .setValueSeparator(String).

Example XML property with default value:

{@code
  
}

@author Chris Beams @author Juergen Hoeller @since 3.1 @see PropertyPlaceholderConfigurer @see org.springframework.context.support.PropertySourcesPlaceholderConfigurer