Category " Apache Wicket"

If you follow anything about Wicket, you know that they just released Wicket 1.4 which offers some very nice improvements and structural changes that make it even more awesome of a framework to work with. Back in March of this year we brought you 5 Days of Wicket, so in today’s post we upgrade the [...]

The Wicket folks have released the latest incarnation of the framework in Apache Wicket 1.4. Notable improvements are: Generified IModel interface and implementations increasing type safety in your Wicket applications Component#getModel() and Component#setModel() have been renamed to getDefaultModel() and setDefaultModel() to better support generified models The Spring modules have been merged (wicket-spring-annot is now obsolete, [...]

In Java land, we’ve become very familiar with jarhell, and the associated pain of trying to find every jar required for let’s say Hibernate. The pain involved in this process is greatly reduced by the use of something like Maven, and while the initial learning curve sucks, you get into a groove with it. What [...]

Does your new Wicket app scream for needing a Google Suggest type component? AutoCompleteTextField in the wicket-extensions package is what you need to fill that void!

A new refcard is available about Apache Wicket is available now. Download it from Mystic’s blog which has all the goodies waiting for you. We’d love to hear about it, and suggestions for future refcardz about Wicket.

DZone has just published a new Refcard by yours truly on their website. See the icon and link below for that, please download it, and read the author interview.

There are four supplied methods in the Wicket framework for changing your configuration from development to deployment and vice-versa. The two possible values for this configuration parameter is “development” or “deployment”.

An introduction that was written earlier this year about setting up a project using Maven, Spring, Hibernate, and getting the entire setup done. Check out the 5 days of Wicket for your dose!

If you’d like to have your FeedbackPanel update with errors in the event of a problem with your form, just adding the FeedbackPanel won’t do you any good. Just as with any other AJAX-updating component in Wicket, you’ll need to add it to the AjaxRequestTarget, only difference is, you’ll have to do this while overriding [...]

When writing AJAX-specific code for Wicket, in order to make any updates to a component, it needs to be added to the AjaxTarget. If you’ve got a particularly large form, this can get tedious, so use an IVisitor instead!