Unable to successfully use gwt-log-3.0.1 in GWT 2.0 hosted mode run using JDK 1.5

[GoogleCodeExporter]

I'm running GWT 2.0.3 on a Windows 7 64 bit machine using a JDK 1.5 JVM 
because that's what our installation of Weblogic uses.

I have configured a module using gwt-log which compiles fine, but when 
running development mode (using JDK 1.5) my modules don't start up but 
instead have this deferred binding issue:

00:00:19.562 [ERROR] Unable to load module entry point class 
com.foobar.gwt_demo.gui.client.DemoModule (see associated exception for 
details)
java.lang.RuntimeException: Deferred binding failed for 
'com.allen_sauer.gwt.log.client.impl.LogImpl' (did you forget to inherit a 
required module?)   
at com.google.gwt.dev.shell.GWTBridgeImpl.create(GWTBridgeImpl.java:43)     
at com.google.gwt.core.client.GWT.create(GWT.java:98)   
at com.allen_sauer.gwt.log.client.Log.<clinit>(Log.java:69)     
at 
com.foobar.shared.userinterface.gui.client.core.CoreModule.onModuleLoad(Cor
eModule.java:102)   
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
9)  
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
l.java:25)  
at java.lang.reflect.Method.invoke(Method.java:585)     
at com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:369)    
at 
com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler
.java:185)  
at 
com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChan
nelServer.java:380)     
at 
com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java
:222)   
at java.lang.Thread.run(Thread.java:595) 
Caused by: java.lang.VerifyError: (class: 
com/google/gwt/core/client/Scheduler, method: <init> signature: ()V) 
Illegal constant pool index     at 
com.google.gwt.dom.client.StyleInjector.schedule(StyleInjector.java:389)    
at com.google.gwt.dom.client.StyleInjector.inject(StyleInjector.java:382)   
at 
com.google.gwt.dom.client.StyleInjector.injectAtStart(StyleInjector.java:27
2)  
at 
com.google.gwt.dom.client.StyleInjector.injectAtStart(StyleInjector.java:25
7)  
at 
com.allen_sauer.gwt.log.client.impl.LogImplBase.<clinit>(LogImplBase.java:6
5)  
at java.lang.Class.forName0(Native Method)  at 
java.lang.Class.forName(Class.java:242)     
at 
com.google.gwt.dev.shell.ModuleSpace.loadClassFromSourceName(ModuleSpace.ja
va:580)     
at 
com.google.gwt.dev.shell.ModuleSpace.rebindAndCreate(ModuleSpace.java:415)  
at com.google.gwt.dev.shell.GWTBridgeImpl.create(GWTBridgeImpl.java:39)     
at com.google.gwt.core.client.GWT.create(GWT.java:98)   
at com.allen_sauer.gwt.log.client.Log.<clinit>(Log.java:69)     
at 
com.foobar.shared.userinterface.gui.client.core.CoreModule.onModuleLoad(Cor
eModule.java:102)   
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
9)  
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
l.java:25)  
at java.lang.reflect.Method.invoke(Method.java:585)     
at com.google.gwt.dev.shell.ModuleSpace.onLoad(ModuleSpace.java:369)    
at 
com.google.gwt.dev.shell.OophmSessionHandler.loadModule(OophmSessionHandler
.java:185)  
at 
com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChan
nelServer.java:380)     
at 
com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java
:222)   
at java.lang.Thread.run(Thread.java:595)

Running in development mode using JDK 1.6, this is not an issue and the 
module works as expected.

Unfortunately, the only JDK I can guarantee on our developer desktops is 
JDK 1.5 (which is what the flavor of Weblogic we are using requires), so 
this is a major roadblock preventing us from rolling out gwt-log.

This thread covers the same issue, along with suggesting 1.6 as the 
workaround:

http://groups.google.com/group/google-web-
toolkit/browse_thread/thread/c15dce2ed5fb83bc/ed7b9790697f3c51?
show_docid=ed7b9790697f3c51

The downloads section lists gwt-log 3.0.1 as being Java 1.5 compatible, and 
it compiles with 1.5, so I'm not sure if there is some complicating factor 
-- we also use the GXT widget toolkit, for instance -- or if there is an 
issue in gwt-log.  Perhaps there is a JDK 1.5 flag that we can set?

Thanks in advance for any help!

Original issue reported on code.google.com by skwee...@gmail.com on 28 Apr 2010 at 10:19

[GoogleCodeExporter]

Looks like this issue:
  http://code.google.com/p/google-web-toolkit/issues/detail?id=4254

Original comment by fredsa@google.com on 29 Apr 2010 at 5:24

• Changed state: Duplicate