Here’s the Deal
Slant is powered by a community that helps you make informed decisions. Tell us what you’re passionate about to get your personalized feed and help others.
When comparing Google Web Toolkit (GWT) vs Apache Wicket, the Slant community recommends Apache Wicket for most people. In the question“What are the best Java web frameworks?” Apache Wicket is ranked 8th while Google Web Toolkit (GWT) is ranked 9th. The most important reason people chose Apache Wicket is:
So it is easy to create, maintain or modify a consistent corporate design across all pages.
Ranked in these QuestionsQuestion Ranking
Common Questions
Other Questions
Pros
Pro Mature & stable (5+ years)
Pro Major backing (Google)
Pro Easy way to create reusable panels or layouts
So it is easy to create, maintain or modify a consistent corporate design across all pages.
Pro Separation of code and layout
The HTML templates contain IDs that are references in Java code. There is no code in the templates.
Pro Valid links in template can be converted to valid links in output html
That way the IDE, e.g. IDEA can verify the links already in the templates and hence there are less bad links.
Pro No configuration mess
Nearly everything is handled in Java code.
Pro Human-friendly URLs
Cons
No cons yet!