GWT is a framework developed by Google to implement AJAX technology. This framework proposes to develop the GUI entirely from Java. This code is then compiled into Javascript, to be embedded in a web application. GWT is composed of a client part, Javascript, which is the GUI application, it communicates with a server developed in Java. Past the discovery of this excellent framework, a question light in my mind: What are the correct patterns and designs code to implement this framework? Let’s take an example, look at the problems and propose improvements to emerge a coherent design. We have a Toy Project, which consists of a login screen. This example, deliberately simplistic, offers the following GUI:
(WWB) is a Wicket component toolkit for displaying and editing JavaBeans. Web pages are automatically generated based on bean properties and conventions. If necessary, the layout, editability, and actions of these pages can be customized. At the highest-level, WWB's BeanForm component provides rich AJAX form functionality. The form is embedded in a Page designed by you. This allows you to create customized page designs and multiple BeanForms to be incorporated on a single page.Other lower-level components may be used independently of BeanForm (e.g., BeanGridPanel). BeanForm makes it very convenient to implement a bean-based form if you don't want to go to a lot of extra work. You focus on the model (beans), Fields within a form are dynamically sent back to the server-side bean as they are changed, which eliminates the typical form submit cycle. This makes WWB act more like a rich client application and less like a standard forms-based application.
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.
The JWIG project investigates design of high-level languages and program analyses for server-oriented Web application programming. JWIG is a Java-based descendant of <bigwig>, which in turn was inspired by MAWL. The current version of JWIG provides: * a flexible method for dynamically generating XHTML documents using a unique template mechanism based on XACT, * a convenient programming model for working with form input, including declarative form field validation using PowerForms, * an explicit language-based model of sessions, and * program analyses that at compile-time guarantee that all documents being generated dynamically are valid XHTML 1.0 and that form input fields always match the code that receives the input.