Why would someone choose Wicket over Struts 2 (or other framework) or viceversa?
I've been working with Wicket for over a month now. My previous experience is with Struts.
If you talk to a Wicket fan, they will tell you about the goods of overcoming the impedance between the stateful OOP and stateless http, componentization and some AJAX support, and that's it. No mention of the issues.
I have my own opinion about the two, good and the bad, but maybe I don't know Wicket enough, so with that said I'd like to hear about the disadvantages of wicket, you know, besides poor documentation and heavy Java development.
Thanks!

Why would someone choose Wicket over Struts 2 (or other framework) or viceversa?
===

I've been working with Wicket for over a month now. My previous experience is with Struts.
If you talk to a Wicket fan, they will tell you about the goods of overcoming the impedance between the stateful OOP and stateless http, componentization and some AJAX support, and that's it. No mention of the issues.
I have my own opinion about the two, good and the bad, but maybe I don't know Wicket enough, so with that said I'd like to hear about the disadvantages of wicket, you know, besides poor documentation and heavy Java development.
Thanks!
