GWT 2.1.1 is now available

Posted by Chris Ramsdale - Friday, December 17, 2010 at 11:26:00 AM

Back in October of this year we released GWT 2.1, with a framework and set of tools that made it easy to build business web apps. Since then we've had some great feedback from the GWT community, and today we're happy to announce that we've incorporated that feedback into our latest release, GWT 2.1.1. The specifics of this release are detailed below, but if you're interested in getting started you can do so here.

For Eclipse users, simply click on the “Google updates available” icon in the lower left hand corner of your screen, or select the “Help->Check for Updates” menu item.

Alongside this release, we’ve also updated the Google Plugin for Eclipse and GWT Designer. Both can be installed via the links below.

The main release updates for each product include:

GWT SDK

GWT’s RequestFactory component, introduced in GWT 2.1, received a lot of attention, both from the GWT team at Google and from the GWT open source community at large. Based on this feedback, we’ve added the following:

  • A service layer, which includes support for non-static service objects
  • Value object support
  • Multiple methods calls on a single request
Google Plugin for Eclipse
  • Improved UiBinder error reporting within SpringSource Tool Suite (STS)
  • Optimized the IDE experience by removing unused Java builders and leveraging the AspectJ fixes in the latest STS release
  • Updated Speed Tracer to perform a full J2EE publish before launching
GWT Designer

If you have questions or want to provide some feedback, we’d love to hear it, and the best place to do so is in the Google Web Toolkit Group.

8 comments:

AutoBean said...

Thank You !
Just in time for Christmas !

I have been struggling with this question.

I was wondering if one choses AutoBean with JSON (instead of RequestFactory)to achieve higher loose coupling in a RESTful architecture (to completely decouple client and server), what would be the downside to this approach ?

Architectural Decisions are about Tradeoff. I want to know what I am going to lose or gain if I chose one over the other.

AutoBean/Editor/EntityProxy/ServiceLayer/EntityChangeEvent

JSON/REST vs EntityProxy/RequestFactory

and how AutoBean fits into all this.

Thank you for the hard work.

Jason Sheedy said...

Good question AutoBean. Our current approach is to go with a JSON/REST service layer using a custom de-serialiser for each Java Bean on the client. Tying the service layer to the GWT RPC protocol adds additional dependency to GWT, but does provide some simplification to the serialization process. I'll be interested to know which way you go.

Charles Bosquet said...

Good work, i'm pleased to see yours efforts on entityProxy !

Maven artifacts are published for GWT 2.1.1 ?

Andigator said...

Excellent! Thanks for the update. Any status on those articles regarding RequestFactory and cell widget integration as mentioned in the docs?

I'm particularly interested in how to handle server-side paging without depending on SQL limits.

Ronaldo Felipe said...

What would most like is a easier and safier way to handle GWT with PHP as backend.
Some kind of php-rpc would be usefull.

Irvan Manalu said...

Thanks for your articel...

GMV Soft said...

Hi Chris, about this point:
* A service layer, which includes support for non-static service objects

are there any documentation?

Thanks.

royal said...

Thnaks For A nice Post.......

web development company