Thanks for your answer. On Feb 24, 6:41 pm, Fred Sauer <[email protected]> wrote: > On Tue, Feb 24, 2009 at 2:16 AM, Arthur <[email protected]> wrote:
> > 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. I see. Personally I'd be happier without those four lines, like in the log4j case. By default it will log to the console albeit not with Level.ALL, so not all messages would be seen. I'm not sure how you could change that without interfering with what the user has configured. Anyone? Regards Arthur --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
