That's an interesting point. I did not know j.u.l was so slow. We need google here, to tell us if their implementation of java.util.logging performance is the same as the vanilla Sun's JVM (don't speak the O name). If this is the case then It's wise to use logback and live with ERROR / INFO only, otherwise I think that a wrapper for logback could be developed that will offload to j.u.l for the log levels.
Maxim. On Wed, Oct 13, 2010 at 10:54 AM, NickA <[email protected]>wrote: > > Just configuring properly log4j/logback to log to System.err or > > System.out should be enough to see messages properly in the AppEngine > > console. > > That's exactly what I used to do but if you read Eurig's blog, that > solution doesn't display the correct log levels in the console. > > "The trouble that I've had is that if you want to make full use of the > nice log highlighting GAE supports in its console then all stdout / > stderr messages will come through as a warning." > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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/google-appengine-java?hl=en.
