client logging config help with unexpected popup

[rjcarr]

I'm using client logging and have been for a while.  Things worked fine in 2.6 but when I switched to 2.7 I got a few logging config errors as handlers were no longer supported.  After correcting these and opening my app in a browser I get a white popup window in the upper left (looks like this http://imgur.com/Xavu6K7).  Strangely, this only shows up when building and running on linux; when running on a mac the popup never appears.

The relevant parts of module file looks like this:

<inherits name="com.google.gwt.logging.Logging"/>


<set-property name="gwt.logging.logLevel" value="CONFIG"/>

<set-property name="gwt.logging.enabled" value="TRUE" />

<set-property name="gwt.logging.consoleHandler" value="ENABLED" />

<set-property name="gwt.logging.developmentModeHandler" value="DISABLED" />

<set-property name="gwt.logging.hasWidgetsHandler" value="DISABLED" />

<set-property name="gwt.logging.systemHandler" value="DISABLED" />

<set-property name="gwt.logging.simpleRemoteHandler" value="DISABLED" />

Basically, all I want is the console handler as I'm doing everything else with a custom handler (it's silly these aren't disabled by default).  My custom handler extends Handler and is pretty simple.  It is created like this:

Logger.getLogger().addHandler(new CustomHandler());

And I'm sure the white popup isn't coming from there.  So what's going on?  And isn't this some sort of GWT defect if things behave differently on different platforms using identical codebases?

Thanks for the help!

[rjcarr]

So I looked at the logging module's xml files and it seems most of the things I'm disabling are disabled by default.  So, I changed my module file to just be this:

<inherits name="com.google.gwt.logging.Logging"/>
<set-property name="gwt.logging.logLevel" value="CONFIG"/>

And I'm still getting the white popup.  Looking at the GWT source code it appears it is coming from LoggingPopup but this is only called by PopupLogHandler.  This should be disabled by the log module here (in LoggingDisabled.gwt.xml which is inherited by Logging.gwt.xml):

<replace-with class="com.google.gwt.logging.client.PopupLogHandler">
 <when-type-is class="com.google.gwt.logging.client.HasWidgetsLogHandler" />
</replace-with>

<set-property name="gwt.logging.hasWidgetsHandler" value="DISABLED" />

But it doesn't seem to be working.  So what am I doing wrong?  I can't be the only one compiling on linux with logging and seeing this, right?

Thanks!

[rjcarr]

One more note: removing the logLevel property didn't change anything, the popup still shows up.  So, at that point, all I'm doing is inheriting the Logging module.

<inherits name="com.google.gwt.logging.Logging"/>

However, if I explicitly disable logging with this:

<set-property name="gwt.logging.enabled" value="FALSE"/>

Then the popup doesn't appear, as expected, but then the logging obviously doesn't work.

I really don't think I'm doing anything out of the ordinary and I'm completely stumped, especially considering I only see this when building and serving from linux.

[Jens]

I am not sure if that also applies to GWT 2.7 as I am using GWT trunk but I had to delete SDM caches to let changes to logging configuration take effect. When SDM starts it tells you which workDir it uses for compilation. Next to that workDir SDM also creates a cache directory named "gwt-cache-<some hash>". Simply delete all these cache folders and also the workDir itself. Then start SDM again to give it a clean start.

When you inherit Logging.gwt.xml then GWT will, by default, only log SEVERE and everything else will be compiled out. If you want a lower level then you need to use

<set-property name="gwt.logging.enabled" value="TRUE"/>

<set-property name="gwt.logging.logLevel" value="INFO"/>

in your own module.

-- J.

[Robert J. Carr]

Thanks for the response, but I'm fairly certain I've never started super dev mode, certainly not on my build server, nor do I see any unexpected cache folders in my working directory.  I like the idea though, maybe there is some other cache I can try? I vaguely remember seeing such a thing but I can't recall where.

>  If you want a lower level then you need to use ... in your own module.

Right, as I said, all I have in my config file is this:

<inherits name="com.google.gwt.logging.Logging"/>

<set-property name="gwt.logging.enabled" value="TRUE"/>

<set-property name="gwt.logging.logLevel" value="CONFIG"/>

Yet I'm still getting the logging popup.  Makes no sense to me.  As I said, it only happens in linux (specifically RHEL and it happened in both 5 and 7 although I don't see how it matters).  It didn't (and doesn't) happen in GWT 2.6.1 with the same exact config.

Thanks for any help you can offer!

> --
> You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/op5aX6OGmMA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.
> To post to this group, send email to google-we...@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.

[jtran]

It's been a while since your last post, but I'm now having the same exact issue as you.  My target environment is RHEL 7, and I'm getting the logger popup.  So far I haven't been able to disable it, but the funny thing is it doesn't appear in SDM when I'm running in my dev (Win7) environment.

Have you managed to disable the popup?  My janky solution is to currently hide it with CSS, but that is only feasible because I don't use PopupPanels in my GWT app.

[Robert J. Carr]

It turned out my problem was mostly my own doing.  I was using different config files in different environments and didn't realize it.  Hope your problem is this simple!