View Javadoc
1   /**
2    * Copyright 2010-2014 The Kuali Foundation
3    *
4    * Licensed under the Educational Community License, Version 2.0 (the "License");
5    * you may not use this file except in compliance with the License.
6    * You may obtain a copy of the License at
7    *
8    * http://www.opensource.org/licenses/ecl2.php
9    *
10   * Unless required by applicable law or agreed to in writing, software
11   * distributed under the License is distributed on an "AS IS" BASIS,
12   * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13   * See the License for the specific language governing permissions and
14   * limitations under the License.
15   */
16  package org.kuali.common.util.log4j.model;
17  
18  /**
19   * @deprecated
20   */
21  @Deprecated
22  public enum Value {
23  
24  	ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, OFF, NULL;
25  	// Log4j only supports "null" (lowercase) as a text value inside log4j.xml
26  	// "NULL" (uppercase) is not supported and causes log4j to emit a WARN level logging message as an unknown level.
27  	// The best solution would be to get log4j to recognize "NULL" as a synonym for "null"
28  	// Failing that, another solution would be to get JAXB to translate "NULL" to "null" and vice versa when writing/reading xml.
29  	// What happens at the moment, is we detect "NULL" and set it to null when creating xml from an object.
30  	// This causes JAXB to omit the "value" attribute entirely from the xml.
31  	// When going the other way (ie creating an object from xml) "NULL" is the default value if the "value" attribute is not present.
32  	// Thus we have a method that works in both directions for dealing with "NULL" vs "null"
33  	// Granted, this is a tad bit crazy and supremely brittle...
34  
35  }