Good stuff. I was getting ready to look into this when I saw your post.

Before Snow Leopard was released this was what I was doing, using 1.5 for hosted mode and 1.6 for the back end code. Now that only 1.6 is available I wanted to see if I could use it instead. On Windows we had a similar issue with 32 bit vs 64 bit jvms, we run 64 bit in production for increased memory use but couldn’t use that for hosted mode debugging. Our build scripts use two environment settings JAVA_HOME and JAVA_EXEC_32 so that the we have definitions for the two jdks we need.

How do you recompile the whole thing before packagint it into a jar?

Awesome, thanks!

When I’m putting this class in my regular source dir in my project in Eclipse, the compiler complains about AWT not being supported (in the initGui method), but jar-ing the class and add it to the projects class path solves that.

This is a great post. Thanks for posting. However I do want to send a bit of a religious message…the fact that Snow Leopard was going to be 64 bit Java was not exactly a secret and I think we, as a community should put more pressure on people like Google to ensure their offerings are ready for things like Snow Leopard. The workaround on their end would be fairly minimal if you think about it, and they could easily offer a simple patch to get this done without the community searching for a solution. Especially since Java 5 is nearing end of service life you’d think products like GWT would have better support for Java 6.

Just my $0.02. Not to take away from a great post on a perfectly legitimate fix while waiting for something from Google.

This is excellent ! Very happy to see an elegant workaround. It took me 2 minutes…and I was back in business.

I was considering the fix with JAVA 1.5 from leopard and hack the links in the System/Library, but I do not want to go there…

Thank you very much !

@MiKey I agree. I was a bit surprised that there wasn’t at least some notice on the GWT web site. Mac users tend to be pretty crazy about upgrading as soon as a new version is out and it’s a shame when something as important to us as GWT is doesn’t work. On the other hand, hurray for release of the source code so that the hack could be made.

I don’t modify the delivered jar, instead the script I use to execute hosted mode includes

-cp “${SRC_PATH}:${OVERRIDE}:${GWT_HOME}/gwt-dev-mac.jar:${GWT_HOME}/gwt-user.jar”

to set the classpath where SRC_PATH is the path to the source code, OVERRIDE is the path to where the BootStrapPlatform class is. In my case OVERRIDE is target/gwtoverride and when I compile my modified BootStrapPlatform class that’s where it goes. So BootStrapPalatform should be picked up from there in preference to the gwt-dev-mac.jar.

If you’re not getting the effect you expect the easiest thing to do is to put a System.out.println statement in the isJava5 method to make sure the right class is getting called.

I wanted to ensure I didn’t forget the ‘-d32′ switch, so I replaced isJava5() with is64bit():

…
public static void initHostedMode() {
/*
* The following check must be made before attempting to initialize Safari,
* or we’ll fail with an less-than-helpful UnsatisfiedLinkError.
*/
if (is64bit()) {
System.err.println(”You must use a 32-bit Java runtime to use GWT Hosted Mode on Mac OS X.”);
System.exit(-1);
}
…
/**
* Determine if we’re using a 64bit runtime
*/
private static boolean is64bit() {
return System.getProperty(”java.vm.name”).contains(”64-Bit”);
}
…

[...] want to give the credits of this Idea (sure is not all mine) to Lombardi and Bizo eclipse, GWT, Mac, Tips Name Email Website [...]

Great information re: GWT 1.7.

Just tonight I noticed in Eclipse it said there was GWT updates so installed them and GWT 1.7.1 installed. I went in to edit it with these changes but the error message was not present. So, I switched my project over to using the new GWT version (1.7.1) and hosted mode fired up without an error.

I’m looking forward to GWT 2.0. Out of process hosted mode will be great, I hope .