RE: how to use sawchain2?

If you're interested in launching Chainsaw2 when your app starts, you could launch is as an appender: appender: org.apache.log4j.chainsaw.ChainsawAppender viewerClass param: org.apache.log4j.chainsaw.LogUI Take care, Scott -Original Message- From: Paul Smith [mailto:[EMAIL PROTECTED

Re: how to use sawchain2?

Try: org.apache.log4j.chainsaw.LogUI.createChainsawGUI(ApplicationPreferenceModel model, Action shutdownAction) method. You will need an instance of the ApplicationPreferenceModel (create a blank one in code and customise it if you need it) and a Swing Action that can handle when the user c

RE: MDC copies

Couldn't this problem be solved by making this (serialization) behavior configurable. Moving the serialization logic out of LoggingEvent and into a strategy class. The default behavior could be identical to existing code. Alternate strategy impls could be written to do other interesting things, lik

how to use sawchain2?

Hi, I tried to instantiate ChainsawCentral like this: import java.awt.*; import javax.swing.*; import org.apache.log4j.chainsaw.plugins.*; public class LoggingDialog extends JDialog { private JPanel panel1 = new JPanel(); private BorderLayout borderLayout1 = new BorderLayout(); private Chains

DO NOT REPLY [Bug 26550] - Incorrect use of appender

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: MDC copies

None of the changes I have made should add any serious performance overhead. Old behavior: MDC.put("name", "value"); (get is similar) - get thread local map - get value from tlm - if value is null - new Hashtable - put new hashtable in tlm - hashtable.put("name", "value"); New behavior: - g

RE: MDC copies

Christian, Adding functionality with computational overhead which is only used with AsyncAppender, does not make sense to me. AsyncAppender is there for performance reasons. Logging asynchronously should not be much slower than direct logging. Unless I am missing something, I think the changes

Re: Thoughs on Level.java

Barry, I think that the "always" printing functionality could be of general use. There are several ways of approaching this. 1) Extending Logger (category) As you have done. Casual users are strongly discouraged from extending the Logger class. A casual user is defined as any developer who is

RE: MDC changes

Howdy, >No one has commented on what I posted before. Am I off base? Any time someone is about to contribute a large scale path affecting several core classes, I like to step back and ask "whoa, this is big, is it necessary? If it's necessary, how come it hasn't been done in the years that log4

MDC changes

No one has commented on what I posted before. Am I off base? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Hierarchical logs in the order of ascending severity.

I'm trying to design logging facility for the application to accomplish the following Loggers: Foo, Foo.Bar and Foo.Baz Configure Foo.Bar and Foo.Baz at priority info and Foo at warning Application may use Foo.Bar and Foo.Baz as appropriate, but warnings, errors etc would also be logged to Foo. T

Re: Thoughs on Level.java

Ceki, Here is a copy of my previous email... Hi, We use Log4J extensively and find that sometimes we alwayswant to log a message, but the message is simply for informationalpurposes. Using Logger/Category.fatal() would potentially frightenu

Re: Thoughs on Level.java

At 02:00 PM 1/30/2004 -0500, Barry Sheward wrote: So Ceki, how would you go about trying to do what I want to do? The alternative to adding four methods to Category is having to subclass Level to include a new Level and use Category.log( Level, ... ) or subclass Category too. Either approach will

Re: Thoughs on Level.java

So Ceki, how would you go about trying to do what I want to do? The alternative to adding four methods to Category is having to subclass Level to include a new Level and use Category.log( Level, ... ) or subclass Category too. Either approach will eventually end up with us writing wrappers around

DO NOT REPLY [Bug 26555] - typo in org.apache.log4j.lf5.util.DateFormatManager

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 26555] - typo in org.apache.log4j.lf5.util.DateFormatManager

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 26555] New: - typo in org.apache.log4j.lf5.util.DateFormatManager

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 26550] New: - Incorrect use of appender

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 26224] - Concurrency policy between AsyncAppender and BoundedFIFO

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 26224] - Concurrency policy between AsyncAppender and BoundedFIFO

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: MDC copies

I have completed the modifications to support a pluggable MDC container. It consists of four new files and patches to ThreadLocalMap, MDC and LoggingEvent. The Web site is not clear on coding conventions or how to send new files (it talks about diff, but I have multiple files...do I just post a hu