[Wicket-develop] Wicket 1.1-rc2 available for testing!

Wed, 05 Oct 2005 14:08:40 -0700

The wicket team is pleased to announce the Wicket 1.1-rc2 release!

http://wicket.sourceforge.net

Wicket is a Java web application framework that takes simplicity, separation
of concerns and ease of development to a whole new level. Wicket pages can be
mocked up, previewed and later revised using standard WYSIWYG HTML design
tools. Dynamic content processing and form handling is all handled in Java
code using a first-class component model backed by POJO data beans that can
easily be persisted using your favourite technology.

Changes in this version include:

  New Features:
  • added class wicket.markup.html.image.resource.BlobImageResource to make working with images from databases easier.
  • Made FileResourceStream non-final to support using custom content type schemas etc
  Fixed bugs:
  • Image components inside a border component are resolved by the parent of the border, thus keeping pre-viewability and componentization. Issue: 1312787. Thanks to Ari Suutari.
  • Borders now treat autolinked resources within wicket:head tags correctly Issue: 1289768. Thanks to Jan Bares.
  • skip content of script tag. Treat it as raw markup Issue: 1287640. Thanks to Jan Bares.
  • Wrong impl. on getParameters() of WebRequestWithCryptedUrl Issue: 1275726.
  • Added serialversionuid to all the serialized wicket classes Issue: 1288373.
  • Link altered child visibility based on wicket id; hidden 'feature' is removed now. Issue: 1297446. Thanks to Sven Meier.
  • Improved hangman letter images to use just one image reference. Issue: 1297449. Thanks to Sven Meier.
  • doc fix for Button.setDefaultFormProcessing Issue: 1287878. Thanks to Leo West.
  • Call invalidate after each setXXX invocation on DefaultButtonImageResource to force re-rendering Issue: 1266998. Thanks to Johan Compagner.
  • Made WicketExampleHeader.html (X)HTML compliant Issue: 1267147. Thanks to Jan Bares.
  • Link.autoEnable is now false by default, and when setEnabled is called, autoEnable will be set to false too as calling setEnabled is a consious action that has no effect when autoEnable is true Issue: 1251658. Thanks to Zhenbang Wei, Niclas Hedhman.
  • Link.autoEnable is now false by default, and when setEnabled is called, autoEnable will be set to false too as calling setEnabled is a consious action that has no effect when autoEnable is true. Autolinks are autoEnabled by default, and so are the paging navigator links. CHECK YOUR CODE WHETHER THIS HAS CONSEQUENCES FOR YOU! Issue: 1240768. Thanks to Gili Tzabari.
  • Models not detached when checkAccess() returns false. Issue: 1290352. Thanks to Phil Kulak.
  • DatePicker fails when used multiple times in the same page Issue: 1290843. Thanks to Ralf Ebert.
  • Buttons with empty value are not found as submit button Issue: 1298789.
  • Persisted form values not loaded for bookmarkable/redirect pages Issue: 1298795.
  • Moved Dojo and Scriptaculous dependencies out of core into contrib packages Issue: 1298082.
  • Renamed pageableListViewNavigation field and getter in PagingNavigator Issue: 1288863. Thanks to Igor Vaynberg.
  • Patch for error in javadoc in ApplicationPages Issue: 1294381. Thanks to Igor Vaynberg.
  • form now checks on enctype attribute. If the attribute is multipart, the multipart property of the form object will be set to that.
  • AJAX component doesn't get correct request parameter path Issue: 1292416.
  Changes:
  • Add WebPage(PageParameters) constructor (helps with your IDE's code completion features) Issue: 1284625. Thanks to Gwyn Evans.
  • made Link.isEnabled non final so that users can more easily customize on/off behaviour.  

Have fun!
-The wicket team

Reply via email to