Martin, log4j is only used if the classes are available server side. If you remove the log4j jar on the server classpath you'll find that JDK logging is used instead.
Fred On Wed, Feb 11, 2009 at 11:39 AM, MWW <[email protected]> wrote: > > I'm attempting to use the RemoteLoggerService with gwt-log, and we're > using slf4j with a logback implementation and the slf4j-log4j adapter > (to route log4j log statements back through slf4j, and into logback. > > It appears that the log4j references are hardcoded rather than using > Apache Commons logging, or another logging framework (SLF4J, in our > case) that allows you to choose the implementation. This is causing > remote logging to fail in the server, due to an exception when looking > up the referenced log4j classes. > > Is there a way we can add our own SLF4J-based RemoteLoggerService? > > Thanks, > > Martin > > > -- Fred Sauer [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 -~----------~----~----~----~------~----~------~--~---
