Versions Compared

Version Old Version 48 New Version 49
Changes made by

Peri Subrahmanya

Peri Subrahmanya

Saved on

Key

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

...

  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 file is also monitored by a background thread and reloaded if changes are made
  4. Going forward, any new logging statements added to OLE FS should use the SLF4J logging api
  5. If existing code is modified, log4j logging calls should be replaced by SLF4J logging calls

PropertiesProperties 

Info

System properties are set by specifying the -D parameter in the VM arguments.

Ex. -Dolefs.configuration=~/.kuali/ole/fs/custiom-configuraiton.properrties - This will tell the app to pick the properties from the above specified location

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

false

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.