Re: Still problems with com.google.gwt.core.client.GWTBridge

I agree with you. 

Passing 'null' did the trick in most cases.

So I just wanted to share my finding as it would not be a big change and would not make a difference in any other case.

On Tuesday, August 27, 2013 4:27:42 PM UTC+2, Thomas Broyer wrote:

On Tuesday, August 27, 2013 4:03:32 PM UTC+2, Stefan Sandhop wrote:

On Wednesday, June 5, 2013 4:32:04 PM UTC+2, Thomas Broyer wrote:

Are you using any third-party GWT library on the server? Which class is trying to access com.google.gwt.core.client.GWT? (rather than com.google.gwt.core.shared.GWT) 

 

For me this happens with com.google.gwt.event.dom.client.PrivateMap using GWT 2.5.1 while trying to create a ClickEvent in a JUnit test (not GWTTestCase). I think, there is no need to use com.google.gwt.core.client.GWT there.

It's possible that using shared.GWT there would solve your immediate problem, but ClickEvent definitely is client code, with lots of JSNI; it's not meant to be used outside a "GWT environment" (i.e. plain JVM), so I think it's unlikely we'd make the change.

Try to refactor your code, or pass 'null' instead of a ClickEvent instance, or have a look at gwt-test-utils or gwt-mockito.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.