The first beta release of wicket 1.2 is available for download. Wicket 1.2 has many improvements and features over Wicket 1.1, including:
- 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 <wicket:message>, better resource bundle lookup strategy
- 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
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, though most of your application's pages and components should not be affected. There is a migration guide available on our wiki:
Migrating to wicket-1.2
This is the first beta release, so not considered production ready. Please help us iron out the last bugs by downloading and testing this beta release.
Have fun!
- the Wicket team
--
Living a wicket life...
Martijn Dashorst - http://www.jroller.com/page/dashorst
Wicket 1.1.1 is out: http://wicket.sourceforge.net/wicket-1.1
