3 ms·
BTW: one more thing which I initially did not mention is that Wicket generates a hell lot of client-side code with loads of nested DIVs (per component probably)
by rauar 14y ago
BTW: one more thing which I initially did not mention is that Wicket generates a hell lot of client-side code with loads of nested DIVs (per component probably), weird and long wicket IDs which tell you nothing (they are automatically created). Pretty tough to get used to - especially for someone trying to understand what happens "under the hood".
- rohshall 14y agoThank you. I was under the impression that Spring MVC (actually Spring, in general) requires a lot of XML configuration. But, maybe it's the best bet now. I checked out Play 2.0. It's a nice framework, but documentation is sparse, which is a show-stopper for a newbie like me.