I'm trying Wicket at the moment. I've used Tapestry 4 and 5 for some years,
along with struts, jsf, spring mvc ... all the usual suspects. I won't get
into the "which is better" argument but I will say that the guys on the
Tapestry mailing list are incredibly helpful. For me this trumps everything
You'll get a richer response from the Tapestry user's mailing list.
Many things are easier in Tapestry, some things are easier in Wicket.
On the whole, the Tapestry code you write will be shorter. You will
not be extending base classes. Unit testing is easier. Integration
testing is the same (us
