Based on some recent discussions, we're going to make a change where we
modify the log levels depending on what UI the user is using. I'll send out
a CL for this shortly.

On Wed, Nov 18, 2009 at 6:07 PM, <[email protected]> wrote:

>
> http://gwt-code-reviews.appspot.com/103812/diff/1/2
> File dev/core/src/com/google/gwt/dev/shell/jetty/JettyLauncher.java
> (right):
>
> http://gwt-code-reviews.appspot.com/103812/diff/1/2#newcode89
> Line 89: logStatus = TreeLogger.TRACE;
> I still object to requiring anyone who wants to see the HTTP logs having
> to specify -logLevel TRACE.  Maybe I am not the average user, but I
> personally look at the web log all the time.  The browser didn't seem to
> do anything?  Check the log and see if it got the host page, then
> hosted.html, etc.  Wondering why the JSONP request didn't get the
> expected results, look at the URL that was used.  Did it get the new
> version of this file or is the browser caching something? Etc.
>
> Switching to TRACE picks up tons more stuff, which means that users who
> *do* want to see these logs will see *more* log results rather than
> less.
>
> If the concern is about how it is presented in GPE, I think a better
> solution is for RemoteUi.getWebServerLogger() to return a new
> PrintWriterTreeLogger with max(logLevel, WARN) instead.
>
>
> http://gwt-code-reviews.appspot.com/103812
>

-- 
http://groups.google.com/group/Google-Web-Toolkit-Contributors

Reply via email to