Wiki source code of Project Wonder Properties Files
Last modified by Theodore Petrosky on 2013/05/22 12:01
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | === This Page will serve as a base location for talking about what can be done with the Properties files using Project Wonder and what properties are available etc. === | ||
| 2 | |||
| 3 | === Precedence === | ||
| 4 | |||
| 5 | When the application launches, Properties files will be loaded in the following order. If there is a conflicting parameter between the files and arguments, the latter one overrides the earlier one. | ||
| 6 | |||
| 7 | 1. Resources/Properties in any frameworks that the application links to | ||
| 8 | 1. Resources/Properties.username in any frameworks that the application links to | ||
| 9 | 1. Resources/Properties in the application itself | ||
| 10 | 1. WebObjects.properties under the home directory (not sure on this file's precedence) | ||
| 11 | 1. Resources/Properties.dev (when app is launched in Development Mode) | ||
| 12 | 1. Resources/Properties.log4j in the application itself (log4j properties) | ||
| 13 | 1. Resources/Properties.log4j.username in the application itself | ||
| 14 | 1. Resources/Properties.database in the application itself (database connection properties) | ||
| 15 | 1. Resources/Properties.database.username in the application itself | ||
| 16 | 1. Resources/Properties.multilanguage in the application itself (encoding properties) | ||
| 17 | 1. Resources/Properties.multilanguage.username in the application itself | ||
| 18 | 1. Resources/Properties.migration in the application itself (migration properties) | ||
| 19 | 1. Resources/Properties.migration.username in the application itself | ||
| 20 | 1. Resources/Properties.frameworkname in the application itself for any frameworks that the application links to | ||
| 21 | 1. Resources/Properties.frameworkname.username in the application itself for any frameworks that the application links to | ||
| 22 | 1. Properties in /etc/WebObjects/YourAppName/ | ||
| 23 | 1. Resources/Properties.username in the application itself | ||
| 24 | 1. Command line arguments | ||
| 25 | |||
| 26 | Regarding the properties in /etc/WebObjects, YourAppName is the name you define in the Monitor, not the the .woa name. And ERXProperties.pathsForUserAndBundleProperties() looks up **only** the "Properties" file name. So your folder can contain only 1 file.Regarding the properties in /etc/WebObjects, YourAppName is the name you define in the Monitor, not the the .woa name. And ERXProperties.pathsForUserAndBundleProperties() looks up **only** the "Properties" file name. So your folder can contain only 1 file. | ||
| 27 | |||
| 28 | === Getting Started: === | ||
| 29 | |||
| 30 | [[About the Properties File>>doc:documentation.Home.WOLips Tutorials.About the Properties file.WebHome]] | ||
| 31 | |||
| 32 | * Variable substitution | ||
| 33 | * Per user property files | ||
| 34 | |||
| 35 | === Available Properties: === | ||
| 36 | |||
| 37 | * DB Properties | ||
| 38 | * ERExtensions Properties | ||
| 39 | * Ajax Properties | ||
| 40 | |||
| 41 | === Note: To set development mode === | ||
| 42 | |||
| 43 | Add the following property: | ||
| 44 | er.extensions.ERXApplication.developmentMode = true (true by default when running Wolips) | ||
| 45 | To turn off development mode: | ||
| 46 | er.extensions.ERXApplication.developmentMode = false |