Tag Archives: tag
Why I’d choose Apache Wicket as a web application framework- part 4
Framework minus points To be fair I have to say something about what I think are the current weakness of the framework: Remember that Wicket has been developed for state-full applications. But there are a number of reasons why you’d … Continue reading
Why I’d choose Apache Wicket as a web application framework- part 3
About Wicket and JS Even from the beginning Wicket had Ajax capabilities built-in that could be called from Java. This is done by simply adding the Java component to an ajax context object, the AjaxRequestTarget. Of course you can invoke … Continue reading
Why I’d choose Apache Wicket as a web application framework- part 2
Component based framework with good concepts that appeals to developers But the best thing for me is that Wicket really feels like a true Object Oriented web framework. All your components, pages, panels are Java objects (with a .html). Every … Continue reading
Why I’d choose Apache Wicket as a web application framework
In a short description Apache Wicket is a good state-full component based framework which cultivates a sound architecture that appeals to Java developers. This is just going to be a general summary of the points of why you might want … Continue reading
