Can you explain why Wicket was so bad for you?
For me personally Wicket was not bad technology wise. There were developers who did had specific things they disliked about the technology, but the main problem was that a lot of components and support code for JSF was simply available.
In this case it came down a little to the Windows vs Linux argument. I hate to use this argument, since I'm a devoted Linux (and OS X) fan, but the thing is that a lot of software is available for Windows, which simply isn't available for Linux. Maybe BeOS/Haiku is an even better example. The technology may be nice, but there is just very little market adoption.
I remember a small incident where a developer had to use a web terminal for some specific application. For JSF a terminal component is readily available (see http://www.primefaces.org/showcase/ui/terminalHome.jsf). For Wicket, no such dice. The developer had to build something from scratch instead. Now this is just an example, and by itself might not mean much, but as it appeared this happened quite a lot.
In addition to that we have build a small but very handy in house library with a number of components, validators and converters for use with JSF. There is a lot of energy going on there and some cool innovations have made this a breeze to use.
In that regard, in our case, Wicket does trail behind. Nobody seems to be really motivated to build up an elegant Wicket util library, so whenever people have to do some work on the Wicket projects that we have they just miss a lot of the ease of use libs that we have. This is thus not really a technical argument of core Wicket vs core JSF, but more a cultural/social argument.
Note: ignorance of a technology is not a good reason for rejecting a of a technology that is "no Wicket skills" very very bad reason to abominate Wicket.
I agree with you, and normally I'm just like that. I use Linux and OS X, which sometimes makes my life a little harder, but I use it anyway since I just like the OS better.
In this case however it's just that everyone knows JSF, we have support tools, supports libs, excellent books and are thus very productive with it. Switching completely to Wicket, which basically not a lot of developers really know is not really a boost for productivity. If Wicket was technically far superior to JSF 2.0 (+ Seam 3 soon), then there might be a point in forcing the adoption to yield a better long term productivity. But after using Wicket for a while, nobody here really thinks Wicket is -way- better. Some things are better in Wicket, some things are better in JSF 2.0.