Comment on TroubleshootingOOPHM in google-web-toolkit

[codesite...@google.com]

Comment by i...@invalidip.com:

I'm using the latest Gwt 2.0.0 rc release with Firefox 3.5.3 on Fedora 8.

After starting the gwt app in debug mode and refreshing the browser a few
times, I then get Firefox to crash. I can provide more info as a backtrace
if needed.

is...@invalidip.com


For more information:
http://code.google.com/p/google-web-toolkit/wiki/TroubleshootingOOPHM

[codesite...@google.com]

Comment by rocky303:

I started two GWT project at a same time, but on different ports (8888 and
8889). Using GWT2.0RC2

[codesite...@google.com]

Comment by kpocie...@o2.pl:

testsetset

[codesite...@google.com]

Comment by gersonjohan:

I tested plugin with Chrome and get this error in Eclipse Plugin:

`com.google.gwt.core.client.JavaScriptException: (RangeError): Maximum call
stack size exceeded`

With others browsers (IE, FF) is very slow or crash

[codesite...@google.com]

Comment by i.mikushin:

Nope! I'm on OpenSolaris, so there is no Firefox plugin for me. I searched
for libgwt_dev_ff35.so sources but only found the binaries in your SVN. I'm
sure there are sources somewhere ;) so that someone could hack a build for
Solaris.

[codesite...@google.com]

Comment by j...@google.com:

The source is at
https://google-web-toolkit.googlecode.com/svn/plugins/xpcom.

The issue you want is
http://code.google.com/p/google-web-toolkit/issues/detail?id=609

I have done some work, but things are complicated by the fact Sun doesn't
support FF3+, Mozilla doesn't have Solaris builds available, and it is a
lot of work to build from source on a marginally supported platform where
there are lots of dependencies. I have it working with FF3.0, but I can't
ship those binaries since I grabbed untrusted binaries to use for the
libraries. As mentioned on that issue, if you are willing to do the work
to get it supported I can help you get it working.

[codesite...@google.com]

Comment by lvjian700:

I'm using the Gwt2.0 and Gxt2.1 with Chome on Win XP
When i visit host page:
http://localhost:8888/WebIM.html?gwt.codesvr=10.2.1.73:9997

Occur this error:

java.lang.VerifyError: (class: com/extjs/gxt/ui/client/widget/Container,
method: adjustIndex signature:
(Lcom/extjs/gxt/ui/client/widget/Component;I)I) Illegal constant pool index
at st.lv.web.im.client.WebIM.onModuleLoad(WebIM.java:20)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
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(BrowserChannelServer.java:380)
at
com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:222)
at java.lang.Thread.run(Unknown Source)

How can i deal with it..

[codesite...@google.com]

Comment by j...@google.com:

This looks like
http://code.google.com/p/google-web-toolkit/issues/detail?id=4254 -- for
now, you will have to use a later JDK.

[codesite...@google.com]

Comment by monish.ar:

Using development mode in Eclipse 3.5 using GWT 2.0 on Windows XP Pro 64
bit, I'm unable to debug as GWT skips most of my Breakpoints. When I
uninstalled the plugin and set my default SDK to 1.7.1, Hosted browser mode
doesn't work anymore. I was asked to install a plugin on IE, which I did
and then I get a compiler error stating that it can't connect to port 9997.
Anyone with such issues?

[codesite...@google.com]

Comment by j...@google.com:

64-bit IE is not currently supported.

[codesite...@google.com]

Comment by monish.ar:

I think GWT 2.0 broke my installation of the previous version. I think I
have to start a new Eclipse install and stick to 1.7.1 for now.

[codesite...@google.com]

Comment by j...@google.com:

You can have multiple versions of GWT installed at once and the current
Eclipse plugin should work with any of them.

Also, GWT 1.7.1 isn't going to give you devmode with a 64-bit browser
either.

[codesite...@google.com]

Comment by monish.ar:

Thanks for your reply. Yeah, actually that's what I assumed. I've had 1.7.1
running until now in the hosted mode without any problems. Once I installed
version 2.0 and started having problems with debugging, I switched back to
1.7.1 SDK but in vain. The problem still remains after version 2.0
uninstall. Since I don't know what exactly went wrong,my only option that
remains is a clean reinstall of Eclipse

[codesite...@google.com]

Comment by yaoancheng:

i feel it hard to use eclipse plugin for gwt2. Reasons are as followed
1. we can not start 2 development mode in the same time;
2. i cant see the development tool in
http://code.google.com/intl/zh-CN/webtoolkit/doc/latest/DevGuideCompilingAndDebugging.html#DevGuideDevMode
i want to see the transfer info in jetty.
3. when we shut down a development server,the tree node is still there.
4. we cant set the default browser to launch,but have to copy the url!!!

can i use gwt2 in the last verson of plugin?

[codesite...@google.com]

Comment by rda...@google.com:

@yaoancheng: Sorry to hear that you're having troubles using the plugin.
Here is some additional information that may help.

Regarding #1, you can actually start two development mode sessions at the
same time. What you need to do is modify the launch configuration so that
the "Automatically Select an Unused Port" option is selected, and add the
following argument to the Program Arguments section:

-codeServerPort auto

Regarding #2, you should see the Development Mode View in Eclipse, instead
of the Development Mode Window. See
http://code.google.com/eclipse/docs/running_and_debugging_2_0.html for a
screenshot.

If you want to see the request log information from Jetty, change the log
level in the launch configuration to TRACE. Then, that information will
show up.

For #3, you can clear out the tree node by clicking on the icon with
overlapping X's. That will clear the nodes for all terminated launches.

As for #4, you are right. That is a feature that we'll add in a future
version of GPE.

If you want to use the plugin, and have the development mode window show up
instead of Eclipse's development mode view, set the "USE_REMOTE_UI"
environment variable FOR YOUR LAUNCH CONFIGURATION to the value "false".

[codesite...@google.com]

Comment by cobracbh:

1. My code could run in FF(3.5.7) and IE(8.0), but not work in
Chrome(4.0.266.0).

Exception was thrown by window with messages: Failed to connect to hosted
mode server at 192.168.2.169：9997

In eclipse, following text was printed:
Exception in thread "Code server for myproj from Mozilla/5.0 (Windows; U;
Windows NT 5.1; en-US) AppleWebKit/532.6 (KHTML, like Gecko)
Chrome/4.0.266.0 Safari/532.6 on
http://localhost:8888/MyProj.html?gwt.codesvr=192.168.2.169:9997 @
rk$A0JQl)"1lx)2u" Exception in thread "Code server for myproj from
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.6 (KHTML,
like Gecko) Chrome/4.0.266.0 Safari/532.6 on
http://localhost:8888/MyProj.html?gwt.codesvr=192.168.2.169:9997 @
1N3M17Kri[!jVr*D"

I have uninstalled all plugins, but still not work.

2. In IE(8.0), when I used chrome frame to access my site, I was told to
install
GWT plugin for chrome instead of I had installed it in chrome. But when I
clicked to install, the link was no response.

Anyway, good job for GWT plugin !

[codesite...@google.com]

Comment by vrinda.pujare:

Currently I am using GWT 2.0.3 with tomcat5.5 as a server, IE6 and
WindowsXP 64bit.
I am trying to debug my application in client debug mode. Also I have
followed all the steps to set up debug mode. And started tomcat and
application using DevMode in debug mode. Debug mode launches the browser
launcher in client debug mode. But when I start debugging application,
breakpoints does not get invoked when I run application in debug mode.
Could any one help me out to figure our what cud be problem wid GWT 2.0.3
debugging?

Thanks in advance.

[codesite...@google.com]

Comment by audiobrian:

The reason of the breakpoints issue, is that maybe you has configured a JRE
and not a JDK. But now I have a question for you. Why you're using Tomcat
with GWT?
Greetings.

[codesite...@google.com]

Comment by Sombr...@gmail.com:

please dudes do something about linux 64 bits and firefox 3.6. It's quite
annoying.

i'm on slackware64 13.1 and firefox 3.6.12, and plugin asks to get
installed again and again and again.

[codesite...@google.com]

Comment by Sombr...@gmail.com:

also, add a flag on configs to enable debug for plugin would be good.

[codesite...@google.com]

Comment by Sombr...@gmail.com:

FYI using firefox 3.5.2 from slackware64 13.0 will get thing working. But
firebug is gone...

[codesite...@google.com]

Comment by rogovskiy:

Chrome plugin is not working. Unable to connect to 9997 works in FF and
Safari (sorta works)

[codesite...@google.com]

Comment by marcello.urbani:

I also had issues with the plugin:
Failed to connect to hosted mode server at 127.0.0.1：9997
Just switched to a random port instead of 9997 in the project settings and
works like a charm :)
Firefox 3.6, but should be a browser independent issue

[codesite...@google.com]

Comment by marcello.urbani:

I also had issues with the plugin:
{{{
Failed to connect to hosted mode server at 127.0.0.1：9997
}}}
Just switched to a random port instead of 9997 in the project settings and
works like a charm :)

Using Firefox 3.6, but should be a browser independent issue

[codesite...@google.com]

Comment by WLiu1976:

Finally make it work on Chrome. The most important thing is to allow the
external web server in the GWT developer plugin. More details see:
http://notepad2.blogspot.com/2010/12/debug-google-web-toolkit-applications.html

[codesite...@google.com]

Comment by flavio.e...@gmail.com:

Can somebody please update
http://code.google.com/webtoolkit/usingeclipse.html with this instructions
or a link? Particularly the way to start the application is a little
misrepresented there...