> ...which are currently configured by what, XML? Doesn't this remove > some of the zero-conf advantages? And, there's going to have to be a > way to configure it in 1.2 somehow also. I guess "almost zero > configuration" isn't as catchy? :-) >
There is configuration, but it's minor and contained in the Application class. Still no XML. If you really want to use XML to configure the Application, the recent Spring integration allows you to do that. Regarding the problem domain issue of Wicket, I've done a lot with it so far and haven't had any problems solving real issues with it, with much less hair-pulling than Struts. I've built a number of Struts applications and consider myself an expert with it, but it's unlikely I'd build another application with Struts while Wicket is available.
