@@ -342,7 +342,7 @@ with placeholder values is defined:
342
342
The example shows properties configured from an external `Properties` file. At runtime,
343
343
a `PropertySourcesPlaceholderConfigurer` is applied to the metadata that replaces some
344
344
properties of the DataSource. The values to replace are specified as placeholders of the
345
- form pass:q[`${property-name}`], which follows the Ant and log4j and JSP EL style.
345
+ form pass:q[`${property-name}`], which follows the Ant, log4j, and JSP EL style.
346
346
347
347
The actual values come from another file in the standard Java `Properties` format:
348
348
@@ -357,9 +357,10 @@ jdbc.password=root
357
357
Therefore, the `${jdbc.username}` string is replaced at runtime with the value, 'sa', and
358
358
the same applies for other placeholder values that match keys in the properties file.
359
359
The `PropertySourcesPlaceholderConfigurer` checks for placeholders in most properties and
360
- attributes of a bean definition. Furthermore, you can customize the placeholder prefix and suffix.
360
+ attributes of a bean definition. Furthermore, you can customize the placeholder prefix, suffix,
361
+ default value separator, and escape character.
361
362
362
- With the `context` namespace introduced in Spring 2.5 , you can configure property placeholders
363
+ With the `context` namespace, you can configure property placeholders
363
364
with a dedicated configuration element. You can provide one or more locations as a
364
365
comma-separated list in the `location` attribute, as the following example shows:
365
366
0 commit comments