For quite a while, I was trying to ignore the increasing buzz about Wicket, convincing myself that I don’t need yet another MVC framework (there are too many of them anyway), but somewhere between the Javalobby articles, the InfoQ article and the O’ReillyNet article – my resolve cracked and I took a closer look. (…)

It looked interesting and so I decided to try and migrate a selected few JSP screens of an existing Spring MVC + Spring WebFlow application to Wicket. This went much better than I expected and two months later (not full time) – I completed migrating the entire app to Wicket and it is now ready for a new release as a 100% JSP free application. (…)

So is Wicket the one true MVC framework that a lot of us have been hunting for? At the moment, I tend to think so. (…)

read the full article

It all sounds so familiar. Spring MVC, Spring WebFlow, XML configuration files, JSP with various tag libraries and custom tags, JSTL, Acegi, an unmaintainable collection of Javascript files and libraries, SiteMesh decorators, Velocity, web-designers who mess up JSP files and so on. Web development like this is error prune and not really suitable for an agile development process.

Wicket sounds very interesting and promising. I should give it a try but I guess I can not convince management to give us some extra weeks to convert the web-application we’ve been working on from Spring MVC to Wicket.

Bookmark It