Versions Compared

Version Old Version 42 New Version 43
Changes made by

Peri Subrahmanya

Peri Subrahmanya

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
titleProperty Loading Order

Order of property loading
1. the properties generated by the ant script (the old way and its still gets run as part of the ant script) - again not to be touched.
2. olefs-default.properties - Within the codebase and should not be touched as it is checked into SVN.
3. configuration.properties (.kuali/ole/fs/configuration.properties) - present on the local machine and generated during the install phase. Can be modified but since it gets generated during the build process, will override any previously customized values.
4. If an external configuration file is present. - local to the developer and doesn't get checked in to SVN. So can point to anywhere in the local system where you hava a valid configuration.properties file.

  1. Runtime property resolution is now possible for OLE FS!
  2. This means the exact same war file can be used for development as well as deployment without altering the binary
  3. Automatically loaded external configuration files are used to reconfigure the binary with machine specific configuration
  4. The default external directory used by OLE FS is now based on the system property user.home
  5. To change this you only have to override one property - ole.fs.home
    1. Properties pointing to other directories needed by OLE FS are expanded into their absolute path at runtime
    2. This way only a single property needs to be overridden (instead of all of them)
  6. The following external property locations are automatically checked and loaded, in this order, if they exist
    1. No Format
      ~/.kuali/ole/fs/configuration.properties
    2. If the system property olefs.configuration is set, the properties file it points to is automatically loaded
  7. If the property ole.fs.runtime.property.expansion=true the following actions are also taken
    1. After loading classpath:configuration.properties load classpath:olefs-default.properties
    2. Expand any properties containing placeholders into their fully resolved equivalents

...