GWT 2.1.1 Release Candidate now available

239 views
Skip to first unread message

Philip Rogers

unread,
Dec 10, 2010, 2:28:32 PM12/10/10
to google-we...@googlegroups.com
    GWT Community,

    We just launched the first release candidate for GWT 2.1.1! You can download this release from the GWT site here: http://code.google.com/p/google-web-toolkit/downloads/list, or as version 2.1.1-rc1 from Maven Central shortly.

    Please be aware that in this release candidate we have introduced three breaking changes from GWT 2.1:
    1.) Request Factory has undergone a major overhaul based on community feedback. Some highlights include support for value objects, easier integration with existing server code via a service layer, and the promotion of the AutoBean framework to a top-level package. The full list of features and details on the breaking API changes are outlined here: http://code.google.com/p/google-web-toolkit/wiki/RequestFactory_2_1_1

    2.) Cell Widgets have been improved with multiple bug fixes, API additions, and new features, including support for multiple selection via the mouse and keyboard. A breaking change has been introduced to the Cell API: a Context object is now passed to most Cell methods and the "key" value is no longer passed. The Context object contains the row and cell index, as well as the "key" value. This change will allow for additional context properties to be passed into Cell methods in the future without breaking API changes.

    3.) The gecko user agent, which corresponds to Firefox 1.0, has been removed. The gecko1_8 user agent, which corresponds to Firefox 1.5 and newer, still remains. If you do not manually set the user agent in your gwt.xml file, you should not notice any change (except one less permutation during compilation). If you do set the user agent in your gwt.xml file, you may need to replace "gecko" with "gecko1_8". If you are referencing "gecko", you are almost definitely getting the wrong behavior for your application because it is using very old code bindings.

    One known issue is that samples/expenses is broken. You can build it by replacing gwt.version 2.1.0 with 2.1.1-rc1 in the Expenses POM; however, you may still encounter Issue 5471 or others.

    Please give it a try and let us know what you think.

    Thanks,
    Philip Rogers on behalf of the Google Web Toolkit team

Jim Douglas

unread,
Dec 10, 2010, 2:42:40 PM12/10/10
to Google Web Toolkit
Philip,

What are the chances of getting this fix backported from trunk to
2.1.1?

http://code.google.com/p/google-web-toolkit/issues/detail?id=1649

On Dec 10, 11:28 am, Philip Rogers <p...@google.com> wrote:
>    GWT Community,
>
>    We just launched the first release candidate for GWT 2.1.1! You can
>    download this release from the GWT site here:
>    http://code.google.com/p/google-web-toolkit/downloads/list, or as version
>    2.1.1-rc1 from Maven Central shortly.
>
>    Please be aware that in this release candidate we have introduced three
>    breaking changes from GWT 2.1:
>    1.) Request Factory has undergone a major overhaul based on community
>    feedback. Some highlights include support for value objects, easier
>    integration with existing server code via a service layer, and the promotion
>    of the AutoBean<http://code.google.com/p/google-web-toolkit/wiki/AutoBean>framework
> to a top-level package. The full list of features and details on
>    the breaking API changes are outlined here:
>    http://code.google.com/p/google-web-toolkit/wiki/RequestFactory_2_1_1
>
>    2.) Cell Widgets have been improved with multiple bug fixes, API
>    additions, and new features, including support for multiple selection via
>    the mouse and keyboard. A breaking change has been introduced to the Cell
>    API: a Context object is now passed to most Cell methods and the "key" value
>    is no longer passed. The Context object contains the row and cell index, as
>    well as the "key" value. This change will allow for additional context
>    properties to be passed into Cell methods in the future without breaking API
>    changes.
>
>    3.) The gecko user agent, which corresponds to Firefox 1.0, has been
>    removed. The gecko1_8 user agent, which corresponds to Firefox 1.5 and
>    newer, still remains. If you do not manually set the user agent in your
>    gwt.xml file, you should not notice any change (except one less permutation
>    during compilation). If you do set the user agent in your gwt.xml file, you
>    may need to replace "gecko" with "gecko1_8". If you are referencing "gecko",
>    you are almost definitely getting the wrong behavior for your application
>    because it is using very old code bindings.
>
>    One known issue is that samples/expenses is broken. You can build
> it byreplacing
>    gwt.version 2.1.0 with 2.1.1-rc1 in the Expenses POM; however, you may
>    still encounter
> Is<http://code.google.com/p/google-web-toolkit/issues/detail?id=5741>
>    s <http://code.google.com/p/google-web-toolkit/issues/detail?id=5741>u<http://code.google.com/p/google-web-toolkit/issues/detail?id=5741>e
>    <http://code.google.com/p/google-web-toolkit/issues/detail?id=5741>54<http://code.google.com/p/google-web-toolkit/issues/detail?id=5741>
>    7 <http://code.google.com/p/google-web-toolkit/issues/detail?id=5741>1<http://code.google.com/p/google-web-toolkit/issues/detail?id=5741>o

zixzigma

unread,
Dec 10, 2010, 4:45:57 PM12/10/10
to Google Web Toolkit
Thank you guys,
that sounds wonderful.
I am very excited about the new features.

zixzigma

unread,
Dec 11, 2010, 3:11:56 AM12/11/10
to Google Web Toolkit
Do you know where I can find JavaDocs for the new features ?
in particular I am looking for Autobean JavaDoc.

Jim Douglas

unread,
Dec 11, 2010, 3:20:43 AM12/11/10
to Google Web Toolkit

monkeyboy

unread,
Dec 16, 2010, 5:59:12 PM12/16/10
to google-we...@googlegroups.com
AFAIK there are another two breaking changes described here:
http://code.google.com/p/google-gin/issues/detail?id=131
and here:
http://code.google.com/p/gwt-google-apis/issues/detail?id=438
I found out about those in version svn 9401. If the changes did not make it to rc1 disregard this post.
Since there are so many breaking changes I think it is misleading to mark this release 2.1.1. Perhaps it should be 2.2.
Reply all
Reply to author
Forward
0 new messages