I´m not alone with my view on Wicket. Just found this on Nabble:

Wicket is the framework that I've been looking for for a long time. The certain feature of wicket that made itself the favorite of mine is it doesn't allow me (and anyone from my co-programmers) to put programming logic in the markup. A little wicket-specific tags, one wicket:id attribute and that's it. Page authors in my team is very happy because they don't have to learn and memorize gazillions of web framework tags anymore. All they have to concern about is html/css/javascript and their beloved Dreamweaver. And aside from this, they can preview the page that they are designing. And they don't have to be bothered anymore by programmers very often.

IMO, this is the true separation of concerns between programmers and visual designers. Programmers have concern only about java code. They don't have to intervene frequently with the designer's markup (majority of programmers can't do visually appealing pages, in the first place). Likewise, designers have concern only about the html pages. They don't have to, or they hate to, see programming logic in the html markup.