GWT 1.5 RC1 now available for download.

[Kelly Norton]

Hi everyone,

We're moving right along with GWT 1.5 and I'm happy to announce that we've posted a release candidate for GWT 1.5 on the Download page.

http://code.google.com/webtoolkit/download.html

This is an exciting release and many of you, eager for Java 5 language support, have already been using it for months. Beyond support for modern Java syntax, there are a lot of other great features. I'll avoid enumerating them here, but many of them are listed in the blog article that announces this release.

http://googlewebtoolkit.blogspot.com/2008/05/google-web-toolkit-15-release-candidate.html

Of course, the best way to check out the new RC is to download it and give it a try. In fact, we're very eager to get your feedback.

/kel

--
If you received this communication by mistake, you are entitled to one free ice cream cone on me. Simply print out this email including all relevant SMTP headers and present them at my desk to claim your creamy treat. We'll have a laugh at my emailing incompetence, and play a game of ping pong. (offer may not be valid in all States).

[rudolf michael]

can't wait to start using it :-)

Thank you guys...

 

[Daniel Kucharski]

Sweet, finally 1.5 support. However, it looks like Google Gears GWT
API is not working anymore?

[ERROR] Errors in 'jar:file:/D:/projecten/gwt-windows-1.5.0/gwt-google-
apis.jar!/com/google/gwt/gears/database/client/ResultSet.java'
[ERROR] Line 58: Type 'long' may not be returned from a JSNI method

Anyone knows when a new gears gwt library will be build?

On 28 mei, 18:34, "Kelly Norton" <knor...@google.com> wrote:
> Hi everyone,
> We're moving right along with GWT 1.5 and I'm happy to announce that we've
> posted a release candidate for GWT 1.5 on the Download page.
>
> http://code.google.com/webtoolkit/download.html
>
> This is an exciting release and many of you, eager for Java 5 language
> support, have already been using it for months. Beyond support for modern
> Java syntax, there are a lot of other great features. I'll avoid enumerating
> them here, but many of them are listed in the blog article that announces
> this release.
>

> http://googlewebtoolkit.blogspot.com/2008/05/google-web-toolkit-15-re...

[Sumit Chandel]

Hi Daniel,

The Google API Libraries for GWT (GALGWT) need to be updated for the
1.5 RC1.

We've recently introduced long emulation in GWT 1.5, meaning that you
can now program against longs in your GWT code and expect that they
will behave appropriately once those longs are running in the
JavaScript world. The downside to this is that longs can no longer be
accessed in JSNI methods because there are no 64-bit integral types in
the JavaScript world. In 1.4, you could get away with returning longs
from JSNI for developers who were fully aware of what their code was
going to do with it, but since it is now emulated in 1.5, the compiler
will report errors for any longs that are being passed into JSNI
methods.

You can read more about this change in the 1.5 release notes
documentation below:
http://code.google.com/docreader/#p(google-web-toolkit-doc-1-5)s(google-web-toolkit-doc-1-5)t(ReleaseNotes_1_5_ImportantNotes)

The team is planning to get the GALGWT libraries fully 1.5 compliant
by the time 1.5 goes final, but until then you will have to either:

1) Stick with 1.4 for a bit if your project heavily depends on the
GALGWT libraries

2) Workaround the problem, or better yet, patch it and contribute the
patch back to us to get GALGWT into shape for 1.5 even faster.

Hope that helps,
-Sumit Chandel

[GregD]

Does not work for me.

Setup: Eclipse 3.3.0, Mac OS/X 1.4.10, 1.5 JVM

Have a "Java Compile" Java "Application" with main class
com.google.gwt.dev.GWTCompiler
If I give it the GWT 1.4.62 jars, it works just fine.
If I give it the GWT 1.5.0 Jars, it
1: deletes my complete web/<module>/WEB-INF folder (not acceptable,
there are jars in there that I use).
2: Complains that it cannot find my RPCImpls classes.

The RPCImpls classes (for example:
class GetSpeciesImpl implements AsyncCallback )

all live in the file RPCImpls.java, which is in the same package as
the main class that uses them. They exist, and 1.4 can find them just
fine, but 1.5 can't.

Greg

[GregD]

If I move my RPCImpls classes into my main class, I instead get the
following error (I'm going to go out on a limb and assume that an
"internal compiler exception" is not MY fault:-) ):

Compiling module edu.ucsc.Grinder.Grinder
Compiling permutations
Analyzing permutation #1
[ERROR] An internal compiler exception occurred
com.google.gwt.dev.jjs.InternalCompilerException: Cycle in
overrides???
at
com.google.gwt.dev.jjs.impl.GenerateJavaScriptAST.mangleNameForPoly(GenerateJavaScriptAST.java:
1792)
at com.google.gwt.dev.jjs.impl.GenerateJavaScriptAST
$CreateNamesAndScopesVisitor.visit(GenerateJavaScriptAST.java:281)
at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:186)
at com.google.gwt.dev.jjs.ast.JVisitor.doTraverse(JVisitor.java:527)
at
com.google.gwt.dev.jjs.ast.JVisitor.doAcceptWithInsertRemove(JVisitor.java:
521)
at
com.google.gwt.dev.jjs.ast.JVisitor.acceptWithInsertRemove(JVisitor.java:
81)
at com.google.gwt.dev.jjs.ast.JClassType.traverse(JClassType.java:62)
at com.google.gwt.dev.jjs.ast.JVisitor.doTraverse(JVisitor.java:527)
at com.google.gwt.dev.jjs.ast.JVisitor.doAccept(JVisitor.java:515)
at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:77)
at com.google.gwt.dev.jjs.ast.JProgram.traverse(JProgram.java:799)
at com.google.gwt.dev.jjs.ast.JVisitor.doTraverse(JVisitor.java:527)
at com.google.gwt.dev.jjs.ast.JVisitor.doAccept(JVisitor.java:509)
at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:69)
at
com.google.gwt.dev.jjs.impl.GenerateJavaScriptAST.execImpl(GenerateJavaScriptAST.java:
1836)
at
com.google.gwt.dev.jjs.impl.GenerateJavaScriptAST.exec(GenerateJavaScriptAST.java:
1634)
at
com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.compile(JavaToJavaScriptCompiler.java:
432)
at com.google.gwt.dev.GWTCompiler.realizePermutation(GWTCompiler.java:
511)
at
com.google.gwt.dev.GWTCompiler.compilePermutations(GWTCompiler.java:
442)
at com.google.gwt.dev.GWTCompiler.distill(GWTCompiler.java:358)
at com.google.gwt.dev.GWTCompiler.run(GWTCompiler.java:564)
at com.google.gwt.dev.GWTCompiler.run(GWTCompiler.java:554)
at com.google.gwt.dev.GWTCompiler.main(GWTCompiler.java:214)
[ERROR] at OrderedSet.java(144): public final Object[]
toArray(Object[] array);

com.google.gwt.dev.jjs.ast.JMethod
[ERROR] at OrderedSet.java(22): class OrderedSet extends
HashSet implements IsSerializable
com.google.gwt.dev.jjs.ast.JClassType
[ERROR] <no source info>: <JProgram>
com.google.gwt.dev.jjs.ast.JProgram
[ERROR] Build failed

[Joseph Gentle]

Hi!

We're looking at using GWT 1.5 for a project for a major bank - but my
managers are all nervous about using a release candidate.

Do you have any (perhaps rough) estimates of when the final version of
GWT1.5 will be ready? Are we talking about ~2 months or ~6 months?

Thanks so much!

-Joseph

On May 29, 2:34 am, "Kelly Norton" <knor...@google.com> wrote:
> Hi everyone,
> We're moving right along with GWT 1.5 and I'm happy to announce that we've
> posted a release candidate for GWT 1.5 on the Download page.
>
> http://code.google.com/webtoolkit/download.html
>
> This is an exciting release and many of you, eager for Java 5 language
> support, have already been using it for months. Beyond support for modern
> Java syntax, there are a lot of other great features. I'll avoid enumerating
> them here, but many of them are listed in the blog article that announces
> this release.
>

> http://googlewebtoolkit.blogspot.com/2008/05/google-web-toolkit-15-re...

[Reinier Zwitserloot]

2 months is far, far more likely at this point. Of course, given that
GWT is an open source project, and given that the GWT core
contributors have never committed to hard data at this point, that's
merely my considered opinion on the matter, nothing you can go print
in a newspaper, if you get my drift.

There are currently 16 open issues that are A) Not fixed yet, and B)
marked for inclusion in RC2. I know for a fact that one of the core
contributors has recently gone through the list and marked a bunch of
obscure stuff for gwt 1.5.1/1.6 so for now that list seems to be
fairly conclusive. Track it yourself by looking at this URL from time
to time:

http://code.google.com/p/google-web-toolkit/issues/list?can=2&q=label%3AMilestone-1_5_RC2+-Status%3AFixedNotReleased&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary&cells=tiles

[Joseph Gentle]

Thanks heaps -- that helps a lot. ... And thank-you for making such a
fabulous tool.

-Joseph

[Quu]

I am playing around with the 1.5RC1 and i found a few things odd in
the "cross browser" behavior while trying to make a library object for
my own projects called NotebookPanel. Strangely the situation is that
IE7 seams to render the way I would expect things, while FF and Safari
don't.. I have one "hack" that I added to make FF and Safari render
one thing right, and have yet to figure out a hack for the second
thing. There is one other bit of wierdness, but i can ignore it for my
purposes (extra padding in a grid under IE)

I am not sure what I should do at this point. I could simply make two
versions of my NotebookPanel, one for IE and one for the rest, and
bind at the library level like some of the official libraries do, but
I am not using anything except the built in GWT ui classes. No custom
Javascript. This is still a RC, so it is possible that this might be a
bug? should I post a link to my code here, or try to fill out a bug
report "issue" with the google code?

otherwise I am having allot of fun with this. I am a java developer,
and have never dabbled in JS or web UI... and having a blast.

[Reinier Zwitserloot]

Go test it in GWT 1.4. 99.9995% of all 'hey, it doesn't look the same
in each browser' issues are simply browser incompatibilities. GWT
tries to fix as many of them as is reasonable, but you'll be old and
very grey before anyone ever gets close 100%.

[Vishal]

Hello Experts,

I have tried to download the http://google-web-toolkit.googlecode.com/files/gwt-windows-1.5.0.zip
with no luck, i am getting below error message when I am trying to
unzip the folder.

get-windows-1.5.0.zip is not valid zip file

Please suggest.

---------------------------
WinZip
---------------------------
Cannot open file: it does not appear to be a valid archive.

If you downloaded this file, try downloading the file again.
---------------------------
OK Help
---------------------------

[LouisB]

Hi,

I downloaded gwt 1.5 rc1 a while back with the intention to use it on
the Google RestDescribe project but after creating a Netbeans 6.1
project using 1.5rc1, compilation results in an out of memory (heap)
problem (even after passing the compiler options to increase the max
memory limit).

I reverted back to gwt 1.4.6 and all is good again.

Has anyone else experienced out of memory problems. Not sure if there
is something specific during the compilation of that code that causes
the compiler to spin out of memory or it's a general problem. I get
the feeling it would run out of memory no matter what the limits are.

I can post a stack trace if that will help.

I think the RestDescribe code base might make a good test case for
GWT1.5 :)

best regards,

Louis

[taggerman]

hey Louis

i got the same issue (i'm assuming that you are using the GWTNB
plugin; go into build-gwt.xml line @13-14 (should be a clickable link
in the build log)
and change :
<java classpath="${javac.classpath}:${src.dir}" failonerror="true"
classname="com.google.gwt.dev.GWTCompiler" fork="true" >
to :
<java classpath="${javac.classpath}:${src.dir}" failonerror="true"
classname="com.google.gwt.dev.GWTCompiler" fork="true"
maxmemory="768M">

note the maxmemory attribute at the end. (unfortunately you need to
remember to do this each time you start netbeans as this is a
generated file.)
changing the netbeans -Xmx arg doesn't work as the build launches a
separate build JVM (fork="true") to which the netbean JVM app args
aren't passed.

hope this helps

-- MM

[jchimene]

On Jul 8, 1:40 am, taggerman <mike.m...@gmail.com> wrote:
> hey Louis
>
> i got the same issue (i'm assuming that you are using the GWTNB
> plugin; go into build-gwt.xml line @13-14 (should be a clickable link
> in the build log)
> and change :
> <java classpath="${javac.classpath}:${src.dir}" failonerror="true"
>               classname="com.google.gwt.dev.GWTCompiler" fork="true" >
> to :
> <java classpath="${javac.classpath}:${src.dir}" failonerror="true"
>               classname="com.google.gwt.dev.GWTCompiler" fork="true"
> maxmemory="768M">
>
> note the maxmemory attribute at the end. (unfortunately you need to
> remember to do this each time you start netbeans as this is a
> generated file.)

<SNIP>

Why not use build.xml and override the <java> element's definition?

build.xml doesn't get wiped out on IDE reload.

Using this technique, I override <target name="debug'> stanza to get -
noserver ${client-url} working.

-30-

[LouisB]

Hi, thanks for the help,

Yes, I'm using the GWTNB plugin.

>Why not use build.xml and override the <java> element's definition?

I don't suppose you have an example of this (I'm not familiar with
what you can do in this file)? Is it the same syntax as the snippet
from taggerman but in build.xml?

I'd like it to be permanent for the project if possible, would save
having to remember to set it all the time!

thanks,

Louis

[LouisB]

Hi, thanks for the help,

Yes, I'm using the GWTNB plugin.

>Why not use build.xml and override the <java> element's definition?

[LouisB]

Right, I see (I think), simply copy the auto-generated section in
build-gwt.xml

and put in build.xml, overridden with the new memory settings, e.g.
something like:

<target name="-post-compile">
<!-- You can override this property in the 'gwt.properties'
file -->
<property name="gwt.compiler.output.style" value="OBFUSCATED"/
>
<property name="gwt.compiler.logLevel" value="WARN"/>

<!-- <java classpath="${javac.classpath}:${src.dir}"

failonerror="true"
classname="com.google.gwt.dev.GWTCompiler" fork="true">

-->

<java classpath="${javac.classpath}:${src.dir}" failonerror="true"
classname="com.google.gwt.dev.GWTCompiler" fork="true"
maxmemory="768M">

<arg value="-out"/>
<arg path="${build.web.dir}/"/>
<arg value="-style"/>
<arg value="${gwt.compiler.output.style}"/>
<arg value="-logLevel"/>
<arg value="${gwt.compiler.logLevel}"/>
<arg value="${gwt.module}"/>
</java>

<property name="gwt.output.dir" value="${gwt.module}"/>

<move todir="${build.web.dir}/${gwt.output.dir}">
<fileset dir="${build.web.dir}/${gwt.module}"/>
</move>
</target>

That seems to have made a difference, thanks everyone :)

[LouisB]

Hmmm, guess what, it now compiles ok but runs out of memory in hosted
mode :) same trick applies I guess...

In general it seems a lot more memory intensive and slower to compile
(& run hosted?) than 1.4.x - is this generally the case?

[vaib]

Hi guys.
Well this is vaibhav and i am making one of my big project in GWT
infact thinking to made in GWT. However i have to shift from the Dojo
framework to GWT as there are many problems in Dojo loke no ide
support etc. This is a major change and can be a big decission taken
by me. I have somewhere come up with the comment that the GWT is not
browser independent. Developers have to made different versions for
the different bwosers. Is it true Please let me made aware of the
fact.

Thank you

cheers,
Vaibhav

[JeanV]

Having the same problem. Everything was working fine under 1.4 but
last night tried to switch to 1.5RC1 and I get the following error in
the shell:

java.lang.OutOfMemoryError: Java heap space

[ERROR] Out of memory; to increase the amount of memory, use the -Xmx
flag at startup (java -Xmx128M ...)

My build.xml:

<java classpath="${javac.classpath}:${src.dir}" failonerror="true"
classname="com.google.gwt.dev.GWTCompiler" fork="true"

maxmemory="2048m" >

<arg value="-out"/>
<arg path="${build.web.dir}/"/>
<arg value="-style"/>
<arg value="${gwt.compiler.output.style}"/>
<arg value="-logLevel"/>
<arg value="${gwt.compiler.logLevel}"/>
<arg value="${gwt.module}"/>
</java>

[JeanV]

Having the same problem. Everything was working fine under 1.4 but
last night tried to switch to 1.5RC1 and I get the following error in
the shell:

java.lang.OutOfMemoryError: Java heap space

[ERROR] Out of memory; to increase the amount of memory, use the -Xmx
flag at startup (java -Xmx128M ...)

My build.xml:

<java classpath="${javac.classpath}:${src.dir}" failonerror="true"
classname="com.google.gwt.dev.GWTCompiler" fork="true"

maxmemory="2048m" >

<arg value="-out"/>
<arg path="${build.web.dir}/"/>
<arg value="-style"/>
<arg value="${gwt.compiler.output.style}"/>
<arg value="-logLevel"/>
<arg value="${gwt.compiler.logLevel}"/>
<arg value="${gwt.module}"/>
</java>

On Jul 13, 3:18 pm, LouisB <chillipower...@gmail.com> wrote:

[Chris Chen]

try adding the -Xmx256m to the java parameters (or 512m/1024m/etc):

<java classpath="${javac.classpath}:${src.dir}" failonerror="true"
classname="com.google.gwt.dev.GWTCompiler" fork="true"
maxmemory="2048m" >

<arg value="-Xmx256m"/>

<arg value="-out"/>
<arg path="${build.web.dir}/"/>
<arg value="-style"/>
<arg value="${gwt.compiler.output.style}"/>
<arg value="-logLevel"/>
<arg value="${gwt.compiler.logLevel}"/>
<arg value="${gwt.module}"/>
</java>

[JeanV]

Ok I managed to get it working. here's the line you need to modify in
build-gwt.xml (note the -Xmx256M addition)

<property name="gwtshell.jvmargs.base" value="-Xmx256m -Xdebug
-Xnoagent -Djava.compiler=none -Xrunjdwp:transport=dt_socket,address=$
{jpda.address.gwt}"/>

On Jul 13, 3:03 pm, LouisB <chillipower...@gmail.com> wrote:
> Right, I see (I think), simply copy the auto-generated section in
> build-gwt.xml
>

> and put in build.xml, overridden with the newmemorysettings, e.g.

[pityug...@gmail.com]

Thank you JeanV that works fine ...

<property name="gwtshell.jvmargs.base" value="-Xmx512M -Xdebug -

Xnoagent -Djava.compiler=none -Xrunjdwp:transport=dt_socket,address=$
{jpda.address.gwt}"/>

I chanfed all of these lines ...

GWT RULEZZZ :D