Versions Compared

Version Old Version 33 New Version 34
Changes made by

Former user

Former user

Saved on

Key

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

...

  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 being deployed on multiple servers 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. Override the single property ole.fs.home to change this
    1. Properties pointing to other directories needed by OLE FS are now automatically derived at runtime by default
    2. This way only a single property needs to be overridden (instead of all of them)
  6. The following external 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

...

  1. A default logging configuration is now bundled into OLE FS
  2. This means logging will work out of the box without requiring you to point OLE FS at an external log4j.properties file
  3. You can still override the default log4j configuration if desired
    1. set the property
      No Format
      ole.fs.log4j.override=true
      1. This can be set as a system property
      2. Or as a property in one of the configuration files that gets automatically loaded
    2. create a log4j.properties containing your custom settings at
      No Format
      ~/.kuali/ole/fs/log4j.properties
    3. OLE FS will use settings from the custom log4j.properties
    4. The custom properties
  4. Any logging added to the application from now on should use SLF4J
  5. As code gets updated, log4j logging statements should get replaced with SLF4J logging statements
    1. file is also monitored by a background thread and reloaded if changes are made
  6. Going forward, any new logging statements added to OLE FS should use the SLF4J logging api
  7. If existing code is modified, log4j logging calls should be replaced by SLF4J logging calls

Properties

Property

Default Value

Description

olefs.configuration

None

If this system property is set, properties are loaded from the location it points to. Properties supplied here, override internal properties

ole.fs.runtime.property.expansion=true/false

true

If true, property expansion is performed at runtime instead of at build time. The resource classpath:olefs-default.properties is loaded if this property is set to true

ole.fs.log4j.override=true/false

false

Set this to true if you want to override the default log4j.properties supplied with the application. This also allows you to alter the log4j configuration at runtime without restarting the application. The log4j.properties file supplied here is monitored by a background thread. It is automatically reloaded when changes are detected.