This certainly seems to be a compiler bug that was introduced in 2.1.1
I tracked this down by brute force using alerts. I turned out to be a
simple
for loop that worked fine in GWT 2.0.2. I added the following

       if (filters[i].getReportColumns() != null) {
        for (int j = 0; j < filters[i].getReportColumns().length; j++)
{
                     do some work here....
        }
        else {
                Window.alert("testing  COLUMNS = NULL");
        }

The alert is never triggered but now the code works fine!!!
All I did was put a null check around the for loop and the generated
code works fine.

Now I am seeing nother 2.1. problem with popup panels and date
pickers. Again
this code worked fine in 2.0.2 and now when I try to select a date via
a date picker
in a popup panel GWT throws the following error:

Uncaught com.google.gwt.event.shared.UmbrellaException: One or more
exceptions caught, see full set in UmbrellaException#getCauses

This fails in both the latest versions of Fire Fox and Chrome but
seems to work in devmode

Once again this code worked fine in GWT 2.0.2

Is anyone else seeing new compiler bugs introduced in GWT 2.1?

-Dale

On Dec 30 2010, 2:11 pm, Oscar Herrera <[email protected]>
wrote:
> I think it might be the same issue I'm having, does this only happens
> to you on hosted mode? or does it happens as well when running on web
> mode?, have you tried setting a log before GWT.create([AnyService])
> and another one after it?, I get to only see the first one, then the
> browser and the GWT console hang and get a message on the server log
> indicating OutOfMemoryException.
>
> I'm using maven instead of ant. My application worked fine up to
> version 2.1M3, after I upgraded to 2.1.0 don't work.
>
> On Dec 28, 4:31 pm, smida02 <[email protected]> wrote:
>
>
>
>
>
>
>
> > I've been using GWT for 2.5 years and haven't really had any problems
> > upgrading until now.
> > I do not use Eclipse for building, I use ANT. Also I should mention
> > that I'm on Linux. I changed my ANT build.xml from
>
> > <fileset id="build.thirdparty.fileset" dir="${thirdparty.dir}">
> >         <include name="gwt-2.0.2/gwt-dnd-3.0.0.jar" />
> >         <include name="gwt-2.0.2/gwt-user.jar" />
> >         <include name="gwt-2.0.2/gwt-dev.jar" />
> >         <exclude name="${ant.dir}/lib/*.jar" />
> >     </fileset>
>
> > to reference the 2.1.1 jars, cleaned and built. I didn't receive any
> > errors but I noticed that the GWT build took a LOT longer than it did
> > in 2.0.2. About 25% longer.
> > When I attempt to run the app it simply hangs and I eventually get the
> > Awe Shucks message as if the JavaScript is in a tight loop. I've also
> > tried this in devmode
> > and the same thing happened. I haven't seen any errors in the devmode
> > console nor have I seen any errors in the browser console.
>
> > I changed my ANT build.xml file back to reference the 2.0.2 jars
> > cleaned and built and the application came up fine. At this point I'm
> > not sure how to get to the bottom of the problem.
> > Any help would be appreciated. Has any one else had similar issues? Is
> > the 2.1.1 GWT complier a lot slower for everyone else?

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Reply via email to