...
For reference material on how native Spring syntax works, see:
Creating New Files
If you need to create your own Spring bean file to import or load into a service's resource set, the following template should be used. While usable to some degree in XML editors, the use of the "p" and "c" shorthand namespaces is not really schema-compatible and is designed for use inside Spring-aware tools such as the Eclipse STS plugin.
...
A key technology that can greatly simplify more complex some Spring syntax is the Spring Expression Language:
Spring expressions in XML configuration are typically bracketed like so: #{ expression }
For just one As a simple example, populating string-list-based properties can require multiple lines of XML, or can be shorthanded with SpEL:
...
By default, idp.home/conf/idp.properties contains the "master" list of properties, and contains a pointer to additional property files, to which you may add your own. All properties are "global" so it doesn't matter which file a property is in; the use of separate files is merely an organizational tool.
| Note |
|---|
If you create your own properties, please avoid prefixing their names with "idp.", as that is reserved for our use. |
Unfortunately, the default syntax for Spring properties clashes with the Velocity macro syntax, which causes conflicts in the attribute resolver configuration. To avoid this problem, the Spring syntax has been customized to use a '%' character as a prefix. So properties in the files will appear as "%{propertyname}" or "%{propertyname:defaultvalue}". If you want to use your own properties, just keep in mind you need to use a different leading character than the "${propertyname}" syntax documented by Spring.
...
The parent bean shown is a utility bean we created to automate the use of a utility function that takes a comma-delimited string and turns it into an array of strings that will automatically turn into a collection inside Spring.
...