|
UsingOOPHM
How to use OOPHM in current trunk.
Phase-Deploy IntroductionPreviously, we have embedded the browser inside GWT hosted mode using SWT. This is unsatisfactory for a number of reasons:
The solution is to invert the problem -- instead of embedding the browser in hosted mode, we will embed a hosted mode plugin in the browser. This has a much smaller footprint that is easier to support, and then we can get support for multiple browsers per platform and cross-machine hosted mode (ie, running hosted mode on Linux and connecting to it from IE on a Windows machine). Installing the PluginYou will need to install a plugin in each browser you intend to use with OOPHM. If you start DevMode in a browser without the plugin, you will get to the page allowing you to install the plugin. If you want to install it ahead of time, you can go directly to that missing-plugin page to install the plugin. The plugins currently available for the following browsers/platforms:
Using OOPHMOOPHM is currently in trunk (it is not and will not be available with any version of GWT earlier than 2.0), and is now enabled by default. If you are using the Eclipse plugin, you may need to manually create a plain Java launch config until version 1.2 is available (1.12 has some support). Note that calls between Java and JS are synchronous, and that means the plugin has to block the browser while a Java method is executing. If you are debugging your Java code, the browser will appear hung until you return back to browser-side code. |
► Sign in to add a comment
Works fine under Linux + eclipse + firefox with rev5111 Really handy !
So far I'm not having much luck (64-bit Ubuntu 9.04). The file gwt-dev-oophm.jar does not exist in the download (gwt-linux-1.6.4), so I'm taking that to mean that the prebuilt oophm-xpcom.xpi requires that I build GWT from svn.
Pulling it down and attempting a build draws the following error (below). The directory 'tools' is present in the top-level directory, but for some reason ant is looking for it one level higher, which is outside of the source tree. I futzed with this a bit, but it's not obvious to me what the fix is.
OOPHM will not work with GWT 1.6, only trunk. See http://code.google.com/webtoolkit/makinggwtbetter.html#workingoncode for details on building GWT from svn.
Regarding Ubuntu 9, you may have issues getting the plugin to work properly there -- some other recent Linux distros have a different library structure for Firefox, so to get it working on FF3 on FC10 I had to use a totally different set of libraries to link against. If after you get GWT built from trunk you have problems using the plugin, let me know and I will work with you to figure it out.
Thanks. I had guessed this value for GWT_TOOLS, but the compile seems not to work (ant 1.7.1, java 64-bit OpenJDK 1.6.0). The first few errors look like
and
which makes me think there are missing dependencies. Poking around a little, it looks like some of these are antlr, checkstyle, and beanutils, which I was able to find packages for. I'm now stuck on 'tapestry':
It'd be helpful to have a description of how to build this on Ubuntu--something like "install these 10 packages, run this command, and it builds".
Excellent! Thanks for this and thanks for the prebuilt pieces for the platforms. I develop on Linux, and must test on IE and Safari. After installing their plugins, I could access the OOPHM app via
from IE and Safari 3 and 4.
Also, for those wishing to run OOPHM from Eclipse Run, open the Run Configurations dialog, select your project, select the Classpath tab, and add gwt-dev-oophm.jar via the "Add External JARs..." button.
Does OOPHM work with current Google Eclipse Plugin? Thanks.
@climbingrose: Yes, just need to add the sdk built from trunk and disable appengine.
P.S. AppEngineLauncher? should override getIconPath() cause returning null causes a NullPointerException? later on.
Actually, instead of disabling appengine you can just use the patch from http://code.google.com/p/google-web-toolkit/issues/detail?id=3560
I am getting errors (build went ok), but on launching from Eclipse in ubuntu, I see the swing window but on the jetty tab I get errors like:
javax.servlet.Servlet 00:00:01.490 WARN? failed jsp javax.servlet.UnavailableException?: Servlet class org.apache.jasper.servlet.JspServlet? is not a javax.servlet.Servlet
00:00:01.492 WARN? failed default javax.servlet.UnavailableException?: Servlet class org.mortbay.jetty.servlet.DefaultServlet? is not a javax.servlet.Servlet
Any ideas on this?
never mind, I have no Idea, I created a new project and now it works with the same jars build earlier...
Where is placed gwt-dev-oophm.jar??
Thanks.
The provided firefox plugin doesn't work for me (Linux x86_64).
I had to build a new firefox plugin from SVN.
Well, I got things to work... once. Most times my App seems to launch and loads the index page and selection script (.nocache.js) but then nothing happens. It doesn't seem to connect back to the HostedMode? server.
If I reload, I get a JS error (as displayed in firebug):
document.body is null http://localhost:8888/UI/UI.nocache.js Line 186
Which is the line:
From function "fetchCompiledScript()" in the selection script.
Any ideas?
I still don't know what I did to get it to work once. But I know it had come up with the above JS error and I hit "Shift-Reload" and I saw a connection in the HostedMode? app, and my GWT app started up in Firefox and worked fine. But it died again when my app tried to open a new window. :-(
OOPHM is broken on pre-Safari 4 and at least IE6/IE7 at the moment. We suspect r5393 broke it, and a fix is being investigated.
Same as mark here, rev 5393 breaks oophm with document.body is null as an error. Reverted to 5392 and it works...
As a complete newbie, this was kinda hard for me to setup on Ubuntu 9.04 64-bit. It sure didn't help being a newbie of all things Eclipse either :P
Anyway, what I did was to build GWT from source from the Compiling guide. Since the Firefox-plug-in didn't work, I had to build that as well (I didn't find the plug-in in the build made from the guide above, is it there?). So I built the oophm-branch as well. This seems a bit overkill just to get the plug-in, maybe there's a flag or something for just building the Firefox plug-in? Well, anyway I used theese commands for that: {{{svn checkout http://google-web-toolkit.googlecode.com/svn/branches/oophm oophm cd oophm ant}}}
After all that work, I had to wrestle Eclipse a bit as well. At first, like the newbie I am, I just added the gwt-dev-oophm.jar to the "top of the classpath" as the text above says, which made it fall under the Bootstrap Entries. This turned out to be the wrong place (it rendered me a HostedMode? error of some sort). You'll want to add it to the top of your project under User Entries like in this newly created project:
- Bootstrap Entries JRE System Library [ia32-java-6-sun-1.6.0.13] - User Entries src - /ProjectName/ - ProjectName (default classpath) ProjectName gwt-dev-oophm.jar - /path/to/gwt-dev-oophm.jar GWT SDK [name version]Also, please note the use of 32-bit JVM. Change your project to using that too. It's in the package repository for Ubuntu 9.04.
Finally I think I'm ready to start playing with GWT. Earlier I used VirtualBox? and a 32-bit install of Ubuntu, but that was just a pain using. Happy coding everyone! :)
Works fine (Windows Vista 32-bit, jdk 1.6.0u13, Eclipse 3.4, GWT trunk rev5557, FireFox? 3.0.11).
With jdk 1.6.0u14, after the page has been opened, it is needed to reload it once more in order to activate breakpoints.
I was trying to follow the Compiling guide and I'm getting the following ant compiling error: BUILD FAILED google/trunk/build.xml:43: The following error occurred while executing this line: google/trunk/platforms.ant.xml:36: The following error occurred while executing this line: google/trunk/platforms.ant.xml:13: The following error occurred while executing this line: google/trunk/dev/core/build.xml:66: The following error occurred while executing this line: google/trunk/common.ant.xml:155: Problem creating jar: /tmp/gwtjar2420128593920631719 (Too many open files)
I'm using Ubuntu 8.10 64 bit Java HotSpot?(TM) 64-Bit Server VM (build 11.2-b01, mixed mode) Apache Ant version 1.7.1
Any ideas, thanks Ken
When I try to start it (Main class=com.google.gwt.dev.HostedMode?) I get: Exception in thread "main" java.lang.NoSuchMethodError?: com.google.gwt.core.ext.ServletContainerLauncher?.getName()Ljava/lang/String;
any ideas what I'm doing wrong? I just put the gwt-dev-oophm.jar at the beginning of my classpath.
Are you trying to use it with GWT 1.6? That isn't going to work.
yeah sorry about that, it somehow mixed up the path. Now I have all libs from trunk and I get: 00:00:19.285 ERROR? Failed to load module 'OOPHMTest' from user agent 'Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.11) Gecko/2009060308 Ubuntu/9.04 (jaunty) Firefox/3.0.11' at bender:47707 java.lang.NoSuchMethodError?: com.google.gwt.dev.shell.StandardGeneratorContext?.<init>(Lcom/google/gwt/dev/javac/CompilationState?;Lcom/google/gwt/dev/cfg/PublicOracle?;Ljava/io/File;Ljava/io/File;Lcom/google/gwt/core/ext/linker/ArtifactSet?;)V at com.google.gwt.dev.shell.ShellModuleSpaceHost?.onModuleReady(ShellModuleSpaceHost?.java:93) at com.google.gwt.dev.shell.ModuleSpace?.onLoad(ModuleSpace?.java:324) at com.google.gwt.dev.shell.OophmSessionHandler?.loadModule(OophmSessionHandler?.java:169) at com.google.gwt.dev.shell.BrowserChannelServer?.run(BrowserChannelServer?.java:149) at java.lang.Thread.run(Thread.java:619)
any ideas what that might be? Firefox opens but the gwt content does not get loaded
Have you tried ant clean build? It looks like you have jars built with different versions of trunk.
you're absolutely right! Did a clean rebuild and now it works - thanks a bunch ;-) Will test and report if anything fails.
I check out trunk #5602 and I am using it on Mac. According to this instruction, I need to do both: remove -XstartOnFirstThread? and SWT jar. I only did the first one and OOPHM seems to be working for me. Does it matter if I do not remove SWT jar from gwt-dev-mac project?
How do you remove XstartOnFirstThread? from the launch config arguments?
yah, I just remove it from the Eclipse launch config.
Hi!
When will be firefox 3.5 supported?
I have successfully got the GWT and OOPHM working on Fedora 11 x86_64. here is what i did.
Downloaded the latest GWT form subversion ( r5632 ) and built it according to the directions linked above. then i had to extract the created SDK ( build/dist/gwt-linux-0.0.0.tar.bz2 ) to some place in my home folder
Downloaded the oophm svn branch
Inside that project I had to make a few changes
[dan@Enigma oophm]$ svn diff Index: plugins/firefox/ScriptableInstance.h =================================================================== --- plugins/firefox/ScriptableInstance.h (revision 5634) +++ plugins/firefox/ScriptableInstance.h (working copy) @@ -70,6 +70,9 @@ JavaObject* createJavaWrapper(int objectId); void destroyJavaWrapper(JavaObject*); + // Fix virtural void problem + void sendFreeValues(HostChannel& channel) { } + static const uint32_t VERSION = 1; private: // Map of object ID to JavaObject Index: plugins/firefox/Makefile =================================================================== --- plugins/firefox/Makefile (revision 5634) +++ plugins/firefox/Makefile (working copy) @@ -1,6 +1,6 @@ INC=-I. -I../common -Inpapi -FLAG32BIT=$(shell ./get32bitflag arch) -CFLAGS=-Wall -g -O2 -fPIC $(INC) -rdynamic -m$(FLAG32BIT) -DLINUX -DBROWSER_NPAPI +FLAG32BIT=64 +CFLAGS=-Wall -g -O2 -fPIC $(INC) -rdynamic -m64 -DLINUX -DBROWSER_NPAPI CXXFLAGS=$(CFLAGS) INSTDIR := extension/platform/$(shell ./getarch arch)/plugins Index: plugins/firefox/install-template.rdf =================================================================== --- plugins/firefox/install-template.rdf (revision 5634) +++ plugins/firefox/install-template.rdf (working copy) @@ -12,7 +12,7 @@ <!-- Firefox 1.5-3.0 supported --> <em:id>{ec8030f7-c20a-464f-9b0e-13a3a9e97384}</em:id> <em:minVersion>1.5</em:minVersion> - <em:maxVersion>3.0.*</em:maxVersion> + <em:maxVersion>3.*</em:maxVersion> </Description> </em:targetApplication> Index: plugins/common/Makefile =================================================================== --- plugins/common/Makefile (revision 5634) +++ plugins/common/Makefile (working copy) @@ -26,7 +26,7 @@ OBJ64= $(patsubst %.cpp,obj64/%.o,$(SRCS)) #all:: libcommon32.a libcommon64.a -all:: libcommon32.a +all:: libcommon64.a libcommon32.a: $(OBJ32) obj32.dir ar -rv $@ $(OBJ32)Then i entered the firefox folder and ran make
then install the build .xpi file with firefox
finally I downloaded the Google Plugin and created a default Web Application Project. For the GWT SDK i pointed it to the custom build one that i made earler ( it comes up as gwt-linux-0.0.0.0 )
After that I just put in the default app and let it fly, no problems so far
The NPAPI plugin (in the firefox directory) is pretty much dead in the water, since it can't handle changing scrolling on the top window -- try running the Mail sample and see if that works.
Also, just putting in an empty sendFreeValues method will cause memory leaks.
Can someone post step-by-step instructions on how to remove -XstartOnFirstThread? from the launch config arguments?
Editing eclipse.ini doesn't help. Thanks
It isn't possible to remove -XstartOnFirstThread? in the latest version of Eclipse:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=211625
http://code.google.com/p/google-web-toolkit/issues/detail?id=3785&can=1&q=kugutsumen
@dan.kozlowski I've followed your steps and it worked like a charm :) thanks a lot. My system: openSUSE 11.1 64bit + FF 3.5rc3 64bit + Sun JVM 1.6 64bit + eclipse 3.4 + GWT trunk (with oophm enabled)
Hi,
did anyone find a workaround for Eclipse and Mac OSX and how to remove the -XstartOnFirstThread? from the classpath when launching from within eclipse?
Actually,
I just added the gwt-dev-oophm.jar to the start of the eclipse launch config, didn't fiddle with the -XstartOnFirstThread? nor the swt classes and started the launch config. No swing window came up, but then from firefox conecting to
http://localhost:8080/MyHtml.html?gwt.hosted=192.168.0.2:9997
I could load the GWT App and better yet while using FF put breakpoints and debug as I was able to do in the former GWT Shell. So as far as i can tell the OOPHM works on Mac OSX and Eclipse by just adding the gwt-dev-oophm.jar to the top of the classpath on the eclipse launch config, only the swing window doesn't appear.
OKAY!! For the extreme newbie out there like myself. I may have an answer for you.
First: My setup is Ubuntu 9.04 in 64 bit mode, with Eclipse 3.4, GWT 1.6, GAE 1.2, Java 1.6 with the OOPHM plug in for firefox 3.0.11
I went through everything on these boards and bits and pieces were hidden here and there. My first real issue was this error...
Exception in thread "main" java.lang.UnsatisfiedLinkError??: /home/bin/packages/eclipse3.4/plugins/com.google.gwt.eclipse.sdkbundle.linux_1.6.4.v200904062334/gwt-linux-1.6.4/libswt-pi-gtk-3235.so: /home/bin/packages/eclipse3.4/plugins/com.google.gwt.eclipse.sdkbundle.linux_1.6.4.v200904062334/gwt-linux-1.6.4/libswt-pi-gtk-3235.so: wrong ELF class: ELFCLASS32 (Possible cause: architecture word width mismatch)
taha had a similar problem on this page: https://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/25d7c210c6b92e59?pli=1
The solution to which was to simply install a 32 bit version of Java, (Java 1.50) and have eclipse point to it under Properties -> Run/Debug Settings -> (select your project) -> edit -> JRE tab.
The next error wasn't mission critical, but nonetheless, it annoyed the heck out of me...
Gtk-Message: Failed to load module "canberra-gtk-module": /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: wrong ELF class: ELFCLASS64
This was solved by following the same steps above but instead of the properties tab hitting the environment tab. Then entering a variable called GTK_PATH and setting the value to /usr/lib32/gtk-2.0
That took care of that. Next up was this error...
com.google.apphosting.utils.jetty.JettyLogger?? warn WARNING: failed greetServlet java.lang.UnsupportedClassVersionError??: Bad version number in .class file
This was solved by our 64 bit cousins on the Mac under this thread http://groups.google.com/group/google-appengine-java/browse_thread/thread/da29f92b3677a1ef
Go to properties again, but this time select Java Compiler. Set the compiler compliance level to 1.5.
That is it. It should fix your issues if you are in a similar boat as me. Try it out and everything should pop up fine and appear to be working.
Or is it...
I guess only time will tell. Thanks to the many that contribute to these boards.
thanks dan. I got the same issues on 64bit platform and I fixed thanks to your tips
I need opera plugin too
Opera is unlikely to ever be supported -- they don't have an open extension API that provides the access to the JS interpreter needed, and the NPAPI support is very limited.
hi. i built trunk over the weekend and launched the Hello sample application using the oophm ant target. I installed the firefox 3.5 extension in a new profile and pointed it to http://localhost:8888/Hello.html?gwt.hosted=127.0.0.1:9997 as instructed by ant. But the browser still says "No GWT Browser Plugin Detected". I'm running debian squeeze on a 64-bit machine. (have no 32-bit libraries or jvm's on my machine). Is there anything i missed? thanks in advance.
Did you build with make BROWSER=ff35, and then install the generated oophm-xpcom-ff35-xpi? What shows up under Tools/Add-ons? If you run firefox from the command line (with no other instances running, or else using -no-remote and a different profile), what messages do you see on stdout/err?
i did have BROWSER=ff35. in Addons, i get "GWT Development Mode Plugin (XPCOM) for FF v3.5+ 0.0.5968M.200916174240". The preferences button is disabled and the "Disable" button is shown. Also firefox(iceweasel) doesn't seem to output anything to the console(even when i pass a -console option). Is there something else i need to enable to see the debug messages that are all over ModuleOOPHM.cpp ?
(i've also tried installing the IE plugin in a virtual windows machine, and then tried the above url after changing localhost and 127.0.0.1 to the linux box's ip address, and i get the same "No GWT Browser Plugin Detected" page)
I got the IE plugin to work on IE8. I guess i can use that for now. I tried installing the firefox extension to FF3.5 on windows but it didn't work there either. I also tried both ff3 and ff3+ on FF3 on windows, and that didn't work either.
Same problems as chetanreddy. Ubuntu 9.04 (32bit). IE does work (in VMWare). Firefox (both 3.0.14, and 3.5.1) are not working (and they used to work with an earlier trunk build). I've tested with the the plugin (.xpi) pointed to by the "No GWT plugin detected" pages.
Update, after building the plugin from the trunk source, FF3 is working.
Firefox 3.5 plugin is available here: http://google-web-toolkit.googlecode.com/svn/trunk/plugins/xpcom/prebuilt/
To install download to local disk and open it in Firefox via File->Open File...
I have successfully compiled trunk and my project works fine compiling with that gwt instead of gwt 1.7. After adding the gwt-dev-oophm.jar to the top of classpath the swing UI changes and it now says it is waiting for a browser to connect to the given URL. I have firefox 3 with the precompiled firefox 3 oophm plugin installed (got it somewhere on google's site as opposed to a precompile from trunk).
Visiting the given URL within FF loads the site correctly and everything works, except Eclipse does not hit any breakpoints and the swing ui still says its waiting for a browser to connect.
Maybe I need to compile the latest code from trunk to make the plugin like dan.kozlowski says? I have installed Cygwin on Vista and running "make" within the oophm/plugins/firefox/ folder gives me several errors.
Does anyone have a suggestion of what I should be doing? Should I try to solve those errors and make the plugin or is that pointless?
Thanks.
If you are using old plugins (ie, not built from trunk), they will work but won't get the full benefit of changes in the Swing UI.
Building on Windows is only supported on Visual Studio, not make in Cygwin, and even there more work needs to be done to update the build files (I have to resurrect my old VMware image I used to build them before).
I don't see how it could be working without connecting to the OOPHM server -- are you sure it didn't open a new tab or create a new session in an existing tab?
Regarding breakpoints, there are couple of possiblities:
Thx for the suggestions tamplinjohn.
I've tried JDK 1.60_07, 1.60_13, 1.60_14, 1.60_16 to no avail.
Launching the OOPHM server does not launch firefox, nor create a new tab nor create a new session in an existing tab. Like I said navigating to the given server URL runs the gwt app 100% perfectly fine, as if it was compiled to JS.
The breakpoints are definitely set on the class files being ran, they are hit when I turn OOPHM off and use the normal gwt browser.
I have tried the prebuilt oophm xpi extension found in oophm\plugins\firefox\prebuilt and I've tried a couple found in trunk\plugins\xpcom\prebuilt\, both the ff3 and ff3+ ones.
Nothing invokes the breakpoints. I've made sure to do clean builds.
I might just have to go back to time old method of using window alerts to debug my app :(
Well ,tried prebuild ff3.5 plugin and it gives me "No GWT plugin found or hosted-mode connection failed" , I am using also ff3 with some old plugin succesfully, so nevermind . It can be platform depended , I am on Arch Linux .
As noted above, the FF plugin is for FF3 only currently. The plugin builds for FF35 from trunk, or will be committed within a few days.
I'm in Windows XP, using the latest FF35 plugin from trunk and compiling my GWT project against the latest from trunk, but I'm still getting the "No GWT plugin found or hosted-mode connection failed" error. I'm also using -noserver. I am definitely running the hosted-mode server. Any ideas?
Am I missing something? Is there supposed to be a "Compile" button in the OOPHM Swing UI?
No, although it may be added back in the final version if we decide exactly how it should work.
@jason.carver: what shows up in Tools->Add Ons for the GWT plugin?
You can run DbgView? and see if the plugin logs messages when it is initialized.
I'm on Mac Leopard and just build GWT from trunk, installed the above link for FF 3.5 OOPHM plugin, ran my module in OOPHM and tried conecting to the app with http://localhost:8080/MyApp.html?gwt.hosted=10.0.2.1:9997, but I also get instantly the message "No GWT plugin found or hosted-mode connection failed". Reading through the comments it seems that more people are having that problem or am I missing something?
@tamplinjoin: I see GWT development mode plugin (XPCOM) for FF3.5+ 0.9.6067M.20090901203601, enabled. In the options, I tried adding a hostname include of localhost:80, but it didn't help.
I tried the DbgView? link, but I'm getting a permissions error. I tried searching for it in the wiki pages, but couldn't find anything.
@tamplinjoin & jason.carver: I've the same problem. Running the latest plugins and builds but it seems the browser won't connect to the server. I only get the latest compiled version of my app...
same problem here with firefox - no connection is established to the hosted mode console. the url is http://localhost:53295/MyApp.html?gwt.hosted=127.0.0.1:9997#M1/StartPage in earlier version there was a new tab for each new connection. the new plugin allows to specify hosts that are allowed to connect (to the plugin?!) - i tried several settings already, but still no luck.
is there some way to see debug output on whether the tcp connection was successful or failed?
What is that DbgView? anyway? Some docs available?
DbgView is available at http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
Thanks for enlighten me. That explains why i don't know it - as a Linux user...
It seems to be a issue that is not living inside of the plugins, as i've tried the inet explorer plugin and the firefox plugin(s) (several version, several plattforms) - none of it was able to connect to the listening hosted debug mode.
a telnet 127.0.0.1 <port> worked... any other ideas?
What is the status of Chromium extension for other platforms? (Linux, Mac)
When running under WindowsXP using FireFox3?.5.2 (and rebuilding the latest GWT trunk) I am able to start using the OOPHM plugin. However, when loading data into my app from the server (during my GWT application startup) I get the following error:
Debug Assertion Failed! Program: C:\Program Files\Mozilla Firefox\firefox.exe File: f:\sp\vctools\crt_bld\self_x86\crt\vsprintf.c Line: 244 Expression: ("Buffer too small", 0)
After this error appears firefox shuts down. The data being loaded at the point of failure is very small in size. All the initial startup config data my GWT application needs was loaded without any errors. Any help would be greatly appreciated.
Additionally, the Internet Explorer OOPHM plugin handles the same GWT application without any errors.
@Martin: For Linux, the output goes to stdout -- just run it from a terminal and you will see it.
@dusan: First they have to ship a version that supported loadable Chrome extensions, and then we will have to see what is required to get a cross-platform security dialog.
@piergrossim: It is possible there is some buffer overflow in the debug logging, since on Windows we do use sprintf to produce output for OutputDebugString?. Can you run DbgView? and see what the last message you get is? That might help narrow down where it is coming from.
I have installed DbgView? and set all available debug trace options on (I have admin perms on system). When I launch Firefox I see alot of debug output. I clear the display then start the OOPHM session. I see a few lines stating startup, urls, etc. I clear the display again then wait for the GWT module to load. From that point on no other debug output is sent, even when I receive the Debug Assertion and Firefox shuts down. I do get the following stack trace inside my IDE: java.net.SocketException?: Connection reset
I have build a 64-bit version of the OOPHM plugin for Safari on Snow Leopard that seems to work good, if anyone is interested. You can get it here.
What changes did you have to make for Snow Leopard? Can you mail a patch to jat@google.com?
about ubuntu 9.04(64 bit) debugging I got it working by using the latest firefox 3.5 plugin from http://google-web-toolkit.googlecode.com/svn/trunk/plugins/xpcom/prebuilt/gwt-dmp-ff35.xpi together with ubuntu`s firefox 3.0 (discovered by accident)
I've got oophm partially working on ubuntu 9.04 (x86_64) using the xpcom prebuilt version from svn and adding the gwt-dev-oophm.jar to the start of the project classpath. I'm also able to browse to the sample greeting application using minefield 3.7a1pre and the ff35 xpcom plugin, but right in there something goes wrong. Here's a traceback:
Yes, it is known they are changing internal APIs in 3.7, so it is not surprising it doesn't work. I doubt any effort will be spent on it until they get closer to release as things may change.
I have already made 2 comments on my issue (check so I don't have to repeat some stuff). I still cannot get oophm to debug. I have tried using the compiled version of GWT from trunk (retrieved from SVN only yesterday Oct 6th) as well as the latest plugin for Firefox 3.0 and IE.
My project compiles and starts up the server fine... it says it is waiting for a browser to connect to the given URL. Going to that URL in FF or IE does run the web app perfectly but no breakpoints are hit.
It is acting the exact same as when I use regular GWT 1.7.1 with the regular GWT hosted mode and I go to the same url (http://localhost:8080/myproject.html) within an external browser such as FF or IE... doing this runs the web app fine but does not invoke breakpoints. The only way breakpoints are invoked is within gwt hosted mode internal browser.
It is acting as it would if I did not even have a plugin installed in the browser.
Dbgview gives absolutely no output whatsoever when launching browsers or running GWT or anything. I have all the capture options on.
Can anyone help me figure out what I am doing wrong?
If it is behaving the same in GWT 1.7.1, it has nothing to do with OOPHM. I would suggest posting on the GWT mailing list for assistance.
In my previous posts I said that when I put gwt-dev-oophm.jar to the top of classpath the swing UI changes from doing hosted mode to the new mode where it depends on a plugin in the browser to connect the javascript to the java code. So no, its not running the same as in GWT 1.7.1 but my experience in the browser is the same, because the plugin appears to not be doing its job. From my perspective it definitely looks like OOPHM is not even happening. So how can it be an issue with regular GWT?
Sorry, I misunderstood what you are saying.
If you are able to connect with the browser plugin and see the tab show up in the Swing UI but your browser isn't hitting the breakpoints, I really have no idea. I have only seen skipped breakpoints with one particular JVM version that has been fixed by Sun.
Basically, the web app runs exactly the same regardless of whether or not the plugin is installed (both FF and IE). Thus it is behaving the same as when using hosted mode in GWT1.7.1 but putting the address (http://localhost:8080/myproject.html) in an external browser (try it, you can use the web app perfectly fine, it just won't hit any breakpoints that way).
I just tried out GWT2.0 milestone 1 and it's the exact same deal. It is supposed to launch FF but it doesn't, doesn't even create a new tab. I tried it without the plugin installed because GWT2.0 is supposed to download and install the correct plugin "the first time you use development mode in a browser that doesn't have the plugin installed" but it did not.
I had been using Eclipse 3.41 but now I am using 3.51, which has not made any difference. I don't know what could be different about my situation compared to anyone else doing OOPHM on windows. I don't suppose it's because I'm running Vista (32bit) is it?
I hope someone might be able to help me with this, because the complexity of what I want to debug is too ridiculous to attempt with window alerts.
You should have a ?gwt.hosted=... portion of the URL -- otherwise the plugin isn't being loaded in your browser (and requires you to have compiled your app to JS).
Yes, the address I posted was the one for hosted mode. Development mode with OOPHM the address is "http://localhost:8080/myproject.html?gwt.hosted=192.168.133.133:9997"
Ya, my app is compiled as well, so maybe the browsers are only being served those files instead of running the Java code synchronously (because my suspicion is that the plugin is not doing anything)
@elmacho: for me the plugin is not even installing - ubuntu 9.04, 64bit, ff 3.0.14
it complains about being not for this version (which obviously is true ;) )
did you do anything else to get it working? i still don't get the tab in the debug mode when i start firefox with the url posted in the eclipse console.
What is the exact message it gives you when rejecting the addon?
I don't have an Ubuntu9 machine to test on, but you could try and see if the version with alternate libraries (needed for Fedora 10 at least) works:
http://google-web-toolkit.googlecode.com/svn/trunk/plugins/xpcom/prebuilt/gwt-dmp-ff3+.xpi
I got debugging to work!
I created a new GWT web app with the Eclipse google plugin using GWT 2.0MS1 as the SDK. This is what most likely solved my problem. Simply changing a project from GWT 1.7.1 to 2.0 must not be making all the necessary changes to the auto generated files to be properly compatible. Obviously this sort of thing will be ironed out for release.
Then I needed to first launch (not a debug launch) the newly created GWT web app (with the default app still intact). I tried this with a browser that did not have the plugin installed (FF3.5) and when navigating to the URL it auto directed me to the plugin install web page and after installing the plugin the web app was rendered correctly. Note that at this point I have not compiled the app so the plugin is indeed doing its job! The java code is what is interacting synchronously with the browser instead of the compiled JS!
Note that I had first attempted to launch the app in debug mode which gave me 3 errors related to the Appengine (com.google.apphosting.utils.jetty... yet eclipse could not resolve com.google.apphosting.utils.jetty) but those errors went away as soon as I did a non debug launch. In other words, the app was able to do a debug launch only after doing a regular launch.
With the debug launch successful I was able to hit a breakpoint in the onModuleLoad method of this default web app! I then copied all the required files from my previous project into this new one. Once again I was able to hit a breakpoint on the onModuleLoad method!
I am very excited to have this working!
if you got "No GWT plugin found or hosted-mode connection failed" try to recompile GWT from trunk.
I had also problems with getting latest plugins to work . We used old trunk build at work so this was problem , I build latest , recompile application and it works again for me .
Hello
I have Firefox 3.0.14 and the OOPHM plugin installed. I can start Jetty but when I try to open the url "http://localhost:8080/MyApplication.html?gwt.hosted=127.0.1.1:9997&" I don't see nothing.
The Jetty log throws the follow warning: "00:03:09,701 WARN? 404 - GET /MyApplication?/1FACB286B2C34CE1F86CFBA1F4ACA76B.cache.html (127.0.0.1) 1434 bytes"
I suppose that this is the application itself, can someone help me?
Thnaks
This error means Firefox tries to load the "compiled" app, i.e. the devel mode plug-in is not detected.
Work fine in Windows XP, Firefox 3.0.13 and Vaddin libraries (http://vaadin.com/wiki/-/wiki/Main/OOPHM%20Step%20by%20Step)
In Windows XP, when I used Firefox/3.5.3 or Firefox/3.0.14, I always had problems below and then my firefox crushed, with an error msg said "Buffer too small". But IE is ok:
com.google.gwt.dev.shell.HostedModeException?: I/O error communicating with client at com.google.gwt.dev.shell.BrowserChannelServer?.invokeJavascript(BrowserChannelServer?.java:173) at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:120) at com.google.gwt.dev.shell.ModuleSpace?.invokeNative(ModuleSpace?.java:502) at com.google.gwt.dev.shell.ModuleSpace?.invokeNativeBoolean(ModuleSpace?.java:190) at com.google.gwt.dev.shell.JavaScriptHost?.invokeNativeBoolean(JavaScriptHost?.java:35) at com.google.gwt.user.client.rpc.impl.RemoteServiceProxy?.isStatsAvailable(RemoteServiceProxy?.java) at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter?.onResponseReceived(RequestCallbackAdapter?.java:209) at com.google.gwt.http.client.Request.fireOnResponseReceivedImpl(Request.java:316) at com.google.gwt.http.client.Request.fireOnResponseReceivedAndCatch(Request.java:288) at com.google.gwt.http.client.Request.fireOnResponseReceived(Request.java:270) at com.google.gwt.http.client.RequestBuilder?$1.onReadyStateChange(RequestBuilder?.java:396) at sun.reflect.GeneratedMethodAccessor63?.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl?.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.google.gwt.dev.shell.MethodAdaptor?.invoke(MethodAdaptor?.java:103) at com.google.gwt.dev.shell.MethodDispatch?.invoke(MethodDispatch?.java:71) at com.google.gwt.dev.shell.OophmSessionHandler?.invoke(OophmSessionHandler?.java:146) at com.google.gwt.dev.shell.BrowserChannel?.reactToMessages(BrowserChannel?.java:1660) at com.google.gwt.dev.shell.BrowserChannelServer?.processConnection(BrowserChannelServer?.java:338) at com.google.gwt.dev.shell.BrowserChannelServer?.run(BrowserChannelServer?.java:195) at java.lang.Thread.run(Unknown Source)
com.google.gwt.dev.shell.BrowserChannel?$RemoteDeathError?: Remote connection lost at com.google.gwt.dev.shell.BrowserChannel?.reactToMessages(BrowserChannel?.java:1675) at com.google.gwt.dev.shell.BrowserChannelServer?.processConnection(BrowserChannelServer?.java:338) at com.google.gwt.dev.shell.BrowserChannelServer?.run(BrowserChannelServer?.java:195) at java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketException?: Connection reset by peer: socket write error at java.net.SocketOutputStream?.socketWrite0(Native Method) at java.net.SocketOutputStream?.socketWrite(Unknown Source) at java.net.SocketOutputStream?.write(Unknown Source) at java.io.BufferedOutputStream?.flushBuffer(Unknown Source) at java.io.BufferedOutputStream?.flush(Unknown Source) at java.io.DataOutputStream?.flush(Unknown Source) at com.google.gwt.dev.shell.BrowserChannel?$ReturnMessage?.send(BrowserChannel?.java:1332) at com.google.gwt.dev.shell.BrowserChannel?$ReturnMessage?.send(BrowserChannel?.java:1337) at com.google.gwt.dev.shell.BrowserChannel?.reactToMessages(BrowserChannel?.java:1663) at com.google.gwt.dev.shell.BrowserChannelServer?.processConnection(BrowserChannelServer?.java:338) at com.google.gwt.dev.shell.BrowserChannelServer?.run(BrowserChannelServer?.java:195) at java.lang.Thread.run(Unknown Source)
How can I do with it? Thanks~
@myonceinalifetime, Thanks! That totally worked for me.
I was having the issue where the plugin would not connect to the server running GWT 2.0 MS1; but creating a new project totally worked.
Looking carefully, it seems like the new project had a different 'gwt-servlet.jar' in the war/WEB-INF/lib/ directory; ie. from the previous GWT installation.
Changing this to the new gwt-servlet.jar from the MS1 got debugging working~
Sooo good. :D :D
I changed the web.xml as follows (although I Replacing that (and fixing the war/WEB-INF/web.xml
Regarding the issue that myonceinalifetime and Douglas.Linder were experiencing, see http://code.google.com/p/google-web-toolkit/issues/detail?id=4126
After suffering a little to get an OOPHM plugin working on debian Iceweasel, I've got success and are making my notes here... hope to help somebody on getting it work too:
On Debian Lenny, with iceweasel (Firefox re-branded) 3.0.6 the .xpi file from this page doesn't works (even the alternate libraries version). To make it work I had to rebuild the plugin linking it against the libraries of the xulrunner-dev package:
to make it work, after building the gwt from trunk as said in Working on Code need to checkout also the plugin-sdks from svn on the same directory level you checked-out tools and trunk:
after this, go to /trunk/plugins/xpcom directory, set some variables and build the thing:
after this, you should have a new gwt-dmp-ff3.xpi file inside the prebuild directory, this file should work with the iceweasel package from lenny.
I think that similar approach need to be taken for packages from squeeze or sid (iceweasel 3.5 already)
tested with iceweasel 3.5 from sid... worked well!
Does OOPHM support chrome://myextension/content/ext.xul?gwt.hosted=localhost:9997 ?
@gwtdeveloper: I don't know if you can use the plugin to debug XUL or not -- if you can get hosted.html loaded in the context of your XUL app it might work. Let us know if you figure out how to make it work, but that isn't something we have time to experiment with at the moment.
I have created a couple of issues for problems being reported here:
I've tried the plugin again - it works fine with newly created GWT projects (from eclipse) - but for our existing application (which is spreaded over several eclipse projects) it doesn't work at all.
@tamplinjohn: I managed to OOPHM to work in XUL by creating a new Linker See http://www.gdevelop.com/w/2009/10/30/using-oophm-to-develop-xul-applications/
getting this when trying to compile trunk (r6688)
[java] Compiling module com.google.gwt.benchmarks.viewer.ReportViewer [java] Compiling 6 permutations [java] Compiling permutation 1... [java] [ERROR] An internal compiler exception occurred [java] com.google.gwt.dev.jjs.InternalCompilerException: Unexpected error during visit. [java] at com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:74) [java] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:239) [java] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:81) [java] at com.google.gwt.dev.jjs.ast.JFieldRef.traverse(JFieldRef.java:109) [java] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:235) [java] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:81) [java] at com.google.gwt.dev.jjs.ast.JConditional.traverse(JConditional.java:68) [java] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:235) [java] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:81) [java] at com.google.gwt.dev.jjs.ast.JConditional.traverse(JConditional.java:68) [java] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:235) [java] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:81) [java] at com.google.gwt.dev.jjs.ast.JConditional.traverse(JConditional.java:68) [java] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:235) [java] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:81) [java] at com.google.gwt.dev.jjs.ast.JReturnStatement.traverse(JReturnStatement.java:39) [java] at com.google.gwt.dev.jjs.ast.JModVisitor$ListContextImmutable.traverse(JModVisitor.java:161) [java] at com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemoveImmutable(JModVisitor.java:284) [java] at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:83) [java] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:235) [java] at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:94) [java] at com.google.gwt.dev.jjs.ast.JMethodBody.traverse(JMethodBody.java:82) [java] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:235) [java] at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:249) [java] at com.google.gwt.dev.jjs.ast.JModVisitor$ListContextImmutable.traverse(JModVisitor.java:161) [java] at com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemoveImmutable(JModVisitor.java:284) [java] at com.google.gwt.dev.jjs.ast.JClassType.traverse(JClassType.java:62) [java] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:248) [java] at com.google.gwt.dev.jjs.ast.JProgram.traverse(JProgram.java:1167) [java] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:235) [java] at com.google.gwt.dev.jjs.impl.JsoDevirtualizer.execImpl(JsoDevirtualizer.java:211) [java] at com.google.gwt.dev.jjs.impl.JsoDevirtualizer.exec(JsoDevirtualizer.java:84) [java] at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:248) [java] at com.google.gwt.dev.jjs.UnifiedAst.compilePermutation(UnifiedAst.java:122) [java] at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:191) [java] at com.google.gwt.dev.ThreadedPermutationWorkerFactory$ThreadedPermutationWorker.compile(ThreadedPermutationWorkerFactory.java:49) [java] at com.google.gwt.dev.PermutationWorkerFactory$Manager$WorkerThread.run(PermutationWorkerFactory.java:70) [java] at java.lang.Thread.run(Thread.java:619) [java] Caused by: java.lang.NoSuchMethodError: com.google.gwt.dev.jjs.impl.MakeCallsStatic.makeStaticCall(Lcom/google/gwt/dev/jjs/ast/JMethodCall;Lcom/google/gwt/dev/jjs/ast/JMethod;)Lcom/google/gwt/dev/jjs/ast/JMethodCall; [java] at com.google.gwt.dev.jjs.impl.JsoDevirtualizer$RewriteVirtualDispatches.endVisit(JsoDevirtualizer.java:70) [java] at com.google.gwt.dev.jjs.ast.JMethodCall.traverse(JMethodCall.java:176) [java] at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:235) [java] ... 36 more [java] [ERROR] at JavaScriptException.java(68): e.getClass() [java] com.google.gwt.dev.jjs.ast.JMethodCall [java] [ERROR] at Class.java(171): e.getClass().typeName [java] com.google.gwt.dev.jjs.ast.JFieldRef [java] [ERROR] at JavaScriptException.java(65): e instanceof String ? "String" : e.getClass().typeName [java] com.google.gwt.dev.jjs.ast.JConditional [java] [ERROR] at JavaScriptException.java(63): e instanceof JavaScriptObject ? JavaScriptException.getName0((JavaScriptObject) e) : e instanceof String ? "String" : e.getClass().typeName [java] com.google.gwt.dev.jjs.ast.JConditional [java] [ERROR] at JavaScriptException.java(61): e == null ? "null" : e instanceof JavaScriptObject ? JavaScriptException.getName0((JavaScriptObject) e) : e instanceof String ? "String" : e.getClass().typeName [java] com.google.gwt.dev.jjs.ast.JConditional [java] [ERROR] at JavaScriptException.java(61): return e == null ? "null" : e instanceof JavaScriptObject ? JavaScriptException.getName0((JavaScriptObject) e) : e instanceof String ? "String" : e.getClass().typeName [java] com.google.gwt.dev.jjs.ast.JReturnStatement [java] [ERROR] at JavaScriptException.java(60): { [java] return e == null ? "null" : e instanceof JavaScriptObject ? JavaScriptException.getName0((JavaScriptObject) e) : e instanceof String ? "String" : e.getClass().typeName; [java] } [java] com.google.gwt.dev.jjs.ast.JBlock [java] [ERROR] at JavaScriptException.java(60): { [java] return e == null ? "null" : e instanceof JavaScriptObject ? JavaScriptException.getName0((JavaScriptObject) e) : e instanceof String ? "String" : e.getClass().typeName; [java] } [java] com.google.gwt.dev.jjs.ast.JMethodBody [java] [ERROR] at JavaScriptException.java(60): private static final String getName(Object e); [java] [java] com.google.gwt.dev.jjs.ast.JMethod [java] [ERROR] at JavaScriptException.java(46): final class JavaScriptException extends RuntimeException [java] com.google.gwt.dev.jjs.ast.JClassType [java] [ERROR] at com.google.gwt.dev.jjs.ast.JProgram(0): <JProgram> [java] com.google.gwt.dev.jjs.ast.JProgram [java] [ERROR] Unrecoverable exception, shutting down [java] com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries) [java] at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.logAndTranslateException(JavaToJavaScriptCompiler.java:935) [java] at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compilePermutation(JavaToJavaScriptCompiler.java:372) [java] at com.google.gwt.dev.jjs.UnifiedAst.compilePermutation(UnifiedAst.java:122) [java] at com.google.gwt.dev.CompilePerms.compile(CompilePerms.java:191) [java] at com.google.gwt.dev.ThreadedPermutationWorkerFactory$ThreadedPermutationWorker.compile(ThreadedPermutationWorkerFactory.java:49) [java] at com.google.gwt.dev.PermutationWorkerFactory$Manager$WorkerThread.run(PermutationWorkerFactory.java:70) [java] at java.lang.Thread.run(Thread.java:619) [java] [ERROR] Not all permutation were compiled , completed (0/6)i got it working with latest trunk. no idea what was changed...
but now i'm facing another problem: "Unknown argument: -style" when trying to launch (via eclipse plugin generated launch file) the application. any workaround available? or do i need a new version of the eclipse plugin for current trunk? if so - where to get it?
Same problem here. After building GWT from trunk I am getting "Unknown argument: -style" when launching my app.
Things are under rapid change as we try and get 2.0 out the door, so you can either go back to released versions of the Eclipse plugin and GWT, or you can wait for the RC when there will be an update to the Eclipse plugin that will work with it.
@Martin, @josetex: the workaround is to create a plain Java launch config (as suggested above) calling com.google.gwt.dev.DevMode? - the only gotcha here is to make sure you set -Xmx256M as a VM argument.
thanks for the hint - works like a charm now. all my previous problems are solved.
Tips to make it work (Ubuntu 9.04 64bits, Eclipse Plugin, -noserver): - Latest release didn't work, I found another one I had on my computer. - Make sure you have ant installed and that it works. - Make sure you have Java 6 32 Bits - You'll have to go to the root directory of the release and run 'ant' - Then go to ./build/dist/ - Then unzip gwt-0.0.0.zip - keep in mind where you unzipped it. - In Eclipse click on your project properties then Google/Web Toolkit/Configure SDK's - Add the new one you just unzipped. - Now you'll have to pray the distribution you're using is not broken or incompatible with your code. (This is where I spent the most time on) - Don't get confused with the posts up here. In the newest distributions there's no more gwt-dev-oophm.jar so don't look for it. It will work out of the box. The new development mode doesn't even support hosted mode. Just look in the Eclipse console and it will give you a url to point your browser to.
Hope it helps someone.
@mauzepeda: Thanks for providing the summary of how to make things work with the current state of trunk and the plugin. I don't think it is necessary that gwt-dev.jar be renamed to gwt-dev-linux.jar though.
This patch will make GAE/Eclipse happy for now, seems to work with no side effects. Patch and build with 'ant dist-dev'.
Index: dev/core/src/com/google/gwt/dev/DevModeBase.java =================================================================== --- dev/core/src/com/google/gwt/dev/DevModeBase.java (revision 6906) +++ dev/core/src/com/google/gwt/dev/DevModeBase.java (working copy) @@ -41,6 +41,7 @@ import com.google.gwt.dev.util.Util; import com.google.gwt.dev.util.arg.ArgHandlerGenDir; import com.google.gwt.dev.util.arg.ArgHandlerLogLevel; +import com.google.gwt.dev.util.arg.ArgHandlerScriptStyle; import com.google.gwt.dev.util.arg.OptionGenDir; import com.google.gwt.dev.util.arg.OptionLogLevel; import com.google.gwt.util.tools.ArgHandlerFlag; @@ -570,6 +571,7 @@ registerHandler(new ArgHandlerGenDir(options)); registerHandler(new ArgHandlerPortHosted(options)); registerHandler(new ArgHandlerRemoteUI(options)); + registerHandler(new ArgHandlerScriptStyle(options)); } }@mark.renouf: Thanks Mark! You saved my day :) BTW have you seen nice new templates for SOYC? now we have yet another place for Google logo to creep on us
@mark.renouf Atfer the patch and build when the app is started in firefox I get a 'GWT module 'xxx' needs to be (re)compiled, please run a compile or use the Compile/Browse button in hosted mode'.
This happens even after compiling the project. Any ideas?
That means you didn't pass the ?gwt.hosted=localhost:9997 in the url
@thomas.matthijs That did the trick, thanks
Is anyone else experiencing extremely slow DevMode? on a mac? I'm using Leopard 10.5.8 with all of the updates and running DevMode? with 64 bit Java 6. I experience the same slowness when using 32 bit Java 5 as well. I'm using 2.0 RC 2 and experience the problem using firefox 3.5.5 and safari.
I am slow experiencing very long load times whenever I hit run or refresh on hosted mode.
I'm also experiencing slowness on Mac OS X Leopard (10.5.8). I'm still on Safari 4.0.3 because of the problems I'd heard that people were having with 4.0.4, however I see the same slowness in Firefox 3.5.5. Where I really notice it is with a GWT-RPC loop that I have. Basically, I'm fetching a batch of results using GWT-RPC and adding them to the view in a loop until there are no more results. It's really fast when compiled and deployed and was slower but tolerable in hosted mode in 1.7. 2.0's development mode, however, is noticeably slower than 1.7's hosted mode. I wonder if it's something to do with serialization of data back to the client or if it's overhead with GWT-RPC calls or server round trips in general.
i use ff 3.7 and plugin not work with this version
@tamplinjohn I believie there is version with loadable extension available quite some time. Is it that difficult to make x-platform dialogs? Wouldn't JS's Window.confirm() do the trick?
When we log into our product we launch a new browser window, also we unfortunately use iFrames as a result of legacy code. Both scenarios make it awkward to set the 'gwt.hosted' property on the appropriate URLs. Has anyone else had a similar issue or aware of a workaround? Is there an alternative to setting that property on the URL?
So when will Windows 7 64 bit + eclipse 64 bit be supported on Windows 7?