Our friends at the former JavaLobby have written up an interview detailing Wicket’s Ajax implementation. Igor, Jonathan and Eelco provide answers, insight and a glimpse of the future of Wicket Ajax.
We just released Wicket 1.3.3 and moved the 1.3 codebase into its own branch to make room for new development.
Johan committed the first go at a generified, Java 5 based Wicket framework during the Wicket Amsterdam Meetup held last tuesday. The meetup was great, and I have video of all the talks. Now I just need to ensure the video is good quality and have to transcode it into a web format. I’ll keep you posted on the progress.
So if you depend on Wicket 1.3 and want to build your own Wicket, you should switch your repository to:
If you are interested in an adventure and dare to move to Java 5 based Wicket you can check out trunk:
Please note that trunk will be in flux during the next couple of weeks while we iron out the wrinkles of moving to Java 5
The most sound advise I’ve heard regarding hiring developers, which I’d consider solid even outside the realm of Apache Wicket development:
Don’t hire Wicket programmers. Hire good OO programmers with real domain problem analysis skills. ? Jonathan Locke
We are in the middle of replacing old Ajax favorite Dojo with Wicket Ajax in our application. The dojo parts are a left over from our pre Wicket 1.2 days when Ajax was still in its infancy. We still have some places where Dojo is used, and this time it triggered a bug. A co-worker said:
“I thought dojos were extinct” ? Sverre
The Wicket team announces the last maintenance release of Wicket 1.2: Wicket 1.2.7.
This release fixes the remaining issues for Wicket 1.2. For future support we ask you to upgrade to Apache Wicket 1.3 or newer.
This release of the Wicket project is not endorsed or approved by the Apache Software Foundation. The Apache Software Foundation is in no way affiliated with this release.
Below are the release notes for Wicket 1.2.7.
- the Wicket team