The
Wicket
project has released the first release candidate of the
1.2 effort.

This release is available on the SourceForge file release system for our project.
You can download the released files on the next link:

This is our first release candidate of the Wicket 1.2
version. We expect to finalize the 1.2 release very soon.
Major features of Wicket 1.2 include:

  • Native, cross-platform AJAX support: use AJAX
    without having to write a single line of
    JavaScript. Wicket's AJAX cross-platform
    capabilities

    have been rated 'A'
  • Render multiple components in one AJAX call,
    where each component can occupy any part of the
    page
  • Improved markup inheritance: panels, pages,
    header contributions
  • Improved and simplified internationalization
    (i18n) support, using ,
    better resource bundle lookup strategy </li>
  • Multiple form component validation, validate two
    or more fields that are related
  • Improved form handling: clear form validation
    workflow that allows you to much easier defined
    required and type conversion attributes of a
    form component
  • Nice URL support through URL mounting
  • Markup fragments (inline panels)
  • Improved performance by replacing OGNL with our
    own object graph language parser
  • Response filter support, added ServerTime and
    ServerClientTime filters
  • Reloading of resource bundles in development
    mode
  • Improved unit test support for your Wicket
    components and pages through the WicketTester,
    create unittests that run outside the container.
  • Out-of-the-box AJAX components: paging
    navigator, link with fallback, auto-updater,
    AJAX form, AJAX submit buttons, etc.
  • Improved authorization and authentication
    support, giving you the power to specify
    authorization at the component level. An example
    project featuring a role based, annotation
    framework is now part of the standard
    distribution.
  • Spring support for injecting your business logic
    into your web pages in a non-intrusive manner,
    while still being able to use the convenient
    Wicket idiom for creating pages (using the Java
    new
    operator).
  • Improved settings system: settings are now
    partitioned into logical groupings to make them
    easier to find
  • Numerous bug fixes and minor improvements
    • </ul>

    The upcoming final Wicket 1.2 release will be a
    major landmark in the history of Wicket and is
    highly anticipated.

    We have tried to keep API changes to a minimum, but
    had to change and remove some methods and classes.
    Wicket 1.2 will not be a drop-in replacement for
    Wicket 1.1 applications (and earlier).
    Most of your application's pages and components
    should not be affected though. There is a migration guide
    available on our wiki:


    Migrating to Wicket 1.2

    This release contains numerous fixes over the Wicket 1.2-beta3 release,
    so you are encouraged to upgrade to 1.2-rc1. We consider the API to
    be stable and expect following releases to be drop-in releases. We do
    keep the right to break this promise in case of a nasty bug.

    We hope you will download and test this release to flesh out the last
    bugs. Have fun!