You don't need to modify Chainsaw - Chainsaw will display (as text) the level provided by the LoggingEvent.
You need to provide a 'receiver' that can use your custom logging level when constructing LoggingEvent instances. For example, you can display java.util.logging levels (as text) when events are received via XmlSocketReceiver configured to use a UtilLoggingXMLDecoder. UtilLoggingXMLDecoder calls UtilLoggingLevel.toLevel(XXXXX) to get a reference to a level and that level is passed in to the LoggingEvent constructor. If you're using a SocketAppender and SocketReceiver and your custom level is available in Chainsaw's classpath, you should be able to display your custom level (as text). Hope this helps, Scott -----Original Message----- From: alex mazour [mailto:[EMAIL PROTECTED] Sent: Wed 3/23/2005 7:49 AM To: [email protected] Cc: Subject: Re: Displaying custom log level in Chainsaw v2 Paul Smith <psmith <at> aconex.com> writes: > > Probably not, there is still the issue of resolving the Level string/int > to a Level. The log4j Level class needs to be changed to enable > 'registration' of custom levels, but I'm not sure how much of a priority > that is at this stage. > > Paul > You mentioned log4j Level class. But log4j already supports custom log levels. It's only the Chainsaw that is unable to handle them. If I were to fix the problem, I'll have to modify Chainsaw only. Is it right ? Thanks, Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
