I have been using Wicket for a while now and I’ve occasionally wondered if GWT provides any kind of advantage over Wicket. Here is a comparison and instead of coding a simple “Hello World” kind of example, here is something a little more complex. Functionality The target functionality is a one-page application that shows data in a single table. Item counts are displayed categorized under multiple “spaces” (workspaces). There is a summary row. The user can click on a space to expand the count of items grouped by status. Some of the tricky parts are: * The number and names of the possible status types can be different for different spaces. * Some of the table cells have to be merged to represent the grouping by space and then by status. * the style / color of the different cells has to be controlled to differentiate the total count from that grouped by status. Let's look at the Java code common to the GWT and Wicket implementations.
I want to start using JPA with Wicket, and the quickest way was to start with Qwicket, a project that already has done the heavy lifting. I wanted to be able to build and run my maven-managed application from eclipse. And lastly, I wanted to use MySQL. Qwicket does come with maven support, but it's managed from an ant script. I wanted native maven support. Here's what I did to change qwicket so it fits my requirements:
Wicket is a lightweight, component-oriented framework that does much to bring the easy, intuitive interfaces found in desktop applications to Java Web development. In this series Nathan Hamblen (of databinder and coderspiel blog ) introduces key aspects of Wicket that differentiate it from other Web application frameworks This first ( of 3 ) article investigates Wicket's virtual state, demonstrating the many ways Wicket accommodates both stateless and stateful Web application development.
Apache Wicket uses so called model objects to bind data objects to Wicket components. The framework provides a number of model implementations to access data
Wicket Web Beans is an Apache Wicket (http://wicket.apache.org) toolkit for JavaBeans. AJAX Web forms are automatically generated from bean properties. The toolkit normally does what you'd expect, but when it doesn't, you can override its behavior.
Java PureFaces is a layer on top of JSF that simplifies implementation. The article here is the aggregate of the blog posts that I have written on our blog. The framework is not yet made public, and we are looking to see if there is interest in us releasing it as an open-source project. We are not a JSF framework company; we develop web applications. This framework is a result of our experience with the tools with which we were already working.
Maven Archetypes for Web Applications
This page contains maven archetypes to help you quickly and easily get started on a web project that uses the jetty plugin. Each archetype allows you to generate a template for your project based on the included sample web application. (This supposes that maven 2.x is already installed in your system)