Arthur, On Tue, Feb 24, 2009 at 2:16 AM, Arthur <[email protected]> wrote:
> > Hi Fred > > Thanks for the gwt-log-project. > > > logger.setUseParentHandlers(false); > > ConsoleHandler consoleHandler = new ConsoleHandler(); > > consoleHandler.setLevel(Level.ALL); > > logger.addHandler(consoleHandler); > > Could you explain the intent behind those lines? Don't they degrade > the logging to the equivalent of a bunch of println() statements? > Wouldn't the idea of using a pre-existing logging framework be to > allow its users to configure it? Like the grand-parent I'd like to use > different logging settings. The problem is that I have to re-set them > as soon as gwt-log gets used. Probably I'm just missing something. Call it laziness on my part. While I've used log4j a lot, I've never had much exposure to JDK logging and just stuck this in there to get going. I wouldn't mind hearing a proposal on how I should handle this so you as an application developer can control the JDK logging in your code while also providing a good 'out of the box' experience. By this I mean that if you did absolutely nothing special in your code then gwt-log would send the JDK logging output to the console by default. Suggestions welcome. Fred > > Thanks > > Arthur > > On Feb 14, 11:52 pm, Fred Sauer <[email protected]> wrote: > > There is some hard coding going on. Please see: > > http://www.google.com/codesearch/p?hl=en#nPuVj14EsSA/trunk/Log/server. > .. > > > > In particular these lines of code are there: > > logger = Logger.getLogger("gwt-log"); > > logger.setUseParentHandlers(false); > > ConsoleHandler consoleHandler = new ConsoleHandler(); > > consoleHandler.setLevel(Level.ALL); > > logger.addHandler(consoleHandler); > > > > Hope that clarifies the behavior you are seeing. > > > > Fred Sauer > > [email protected] > > > > On Tue, Dec 30, 2008 at 12:55 AM, akutz <[email protected]> wrote: > > > > > Quick question - on the server side I am also using gwt-log, but it > > > does not seem to respect my settings in the properties file. I have it > > > configured to spit out DEBUG messages with: > > > > > log4j.logger.gwt-log=DEBUG, gwt-log > > > log4j.appender.gwt-log=org.apache.log4j.ConsoleAppender > > > log4j.appender.gwt-log.layout=org.apache.log4j.PatternLayout > > > log4j.appender.gwt-log.layout.ConversionPattern=[%p] "%d{yyyy-MM-dd > > > HH:mm:ss:SSS}" %m%n > > > > > However, when I change it to ERROR, all the messages keep coming, even > > > those logged with Log.debug(String). Thoughts? > > > > > > > -- Fred Sauer Developer Advocate Google Inc. 1600 Amphitheatre Parkway Mountain View, CA 94043 [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-log" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/gwt-log?hl=en -~----------~----~----~----~------~----~------~--~---
