001package org.kuali.common.util.log4j.model;
002
003/**
004 * @deprecated
005 */
006@Deprecated
007public enum Value {
008
009        ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF, NULL;
010        // Log4j only supports "null" (lowercase) as a text value inside log4j.xml
011        // "NULL" (uppercase) is not supported and causes log4j to emit a WARN level logging message as an unknown level.
012        // The best solution would be to get log4j to recognize "NULL" as a synonym for "null"
013        // Failing that, another solution would be to get JAXB to translate "NULL" to "null" and vice versa when writing/reading xml.
014        // What happens at the moment, is we detect "NULL" and set it to null when creating xml from an object.
015        // This causes JAXB to omit the "value" attribute entirely from the xml.
016        // When going the other way (ie creating an object from xml) "NULL" is the default value if the "value" attribute is not present.
017        // Thus we have a method that works in both directions for dealing with "NULL" vs "null"
018        // Granted, this is a tad bit crazy and supremely brittle...
019
020}