Application properties present named data of different types, which determine various aspects of application configuration and functions.
Application properties can be classified by the intended purpose as follows:
-
Configuration parameters – specify sets of configuration files and certain user interface parameters, i.e. determine the application functionality.
For example: cuba.springContextConfig, cuba.web.useLightHeader.
-
Deployment parameters – describe different URLs to connect application blocks, DBMS type, security subsystem settings etc.
For example: cuba.connectionUrlList, cuba.dbmsType, cuba.userSessionExpirationTimeoutSec.
-
Runtime parameters – audit settings, email sending parameters etc.
For example: cuba.security.EntityLog.enabled, cuba.email.smtpHost.
Typically, a property belongs to one or several application blocks. For example, cuba.persistenceConfig is only intended for Middleware, cuba.web.useLightHeader belongs to Web Client, while cuba.springContextConfig is used in all blocks.
Belonging to a block means that if you need to set some value to a property, you should do it in all blocks, used in the application, to which this property belongs.
You can find out where a property belongs as per below:
-
From the documentation: See Appendix B, Application Properties.
-
By tracing property usage in the application code.
-
If a property has an access via configuration interface, by project module owning the interface .
