Before applying this - has anyone looked at the impliciations with respect to framework.logger and the other log drivers. Is this a feature that would/should/could be propergated into logger.Logger or whould that conflict with the other logging solutions? If there is a conflict, is there a tangible benefit in adding the feature to log.Priority ?

Cheers, Steve.


Peter Donald wrote:

Redirecting to avalon-dev. Could someone apply this?

On Wed, 27 Nov 2002 09:42, Tony Thompson wrote:

Index: src/java/org/apache/log/Priority.java
===================================================================
RCS file:
/home/cvspublic/jakarta-avalon-logkit/src/java/org/apache/log/Priority.java
,v retrieving revision 1.12
diff -u -r1.12 Priority.java
--- src/java/org/apache/log/Priority.java 20 May 2002 10:12:49 -0000 1.12
+++ src/java/org/apache/log/Priority.java 26 Nov 2002 22:38:56 -0000
@@ -45,6 +45,11 @@
*/
public static final Priority FATAL_ERROR = new Priority(
"FATAL_ERROR", 25 );

+ /**
+ * Do not log anything.
+ */
+ public static final Priority NONE = new Priority( "NONE",
Integer.MAX_VALUE ); +
private final String m_name;
private final int m_priority;

@@ -66,6 +71,8 @@
return Priority.ERROR;
else if( Priority.FATAL_ERROR.getName().equals( priority ) )
return Priority.FATAL_ERROR;
+ else if( Priority.NONE.getName().equals( priority ) )
+ return Priority.NONE;
else
return Priority.DEBUG;
}


--

Stephen J. McConnell

OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net




--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to