The Full Wiki

WebWork: Wikis


Note: Many of our articles have direct quotes from sources you can cite, within the Wikipedia article! This article doesn't yet, but we're working on it! See more info or our list of citable articles.


From Wikipedia, the free encyclopedia

Developer(s) OpenSymphony
Stable release 2.2.6 / 2007-07-21; 2 years ago
Written in Java (programming language)
Operating system Cross-platform
Development status Unmaintained
Type Web Framework
License Apache License 2.0

WebWork was a Java-based web application framework developed by OpenSymphony that merged into the current Struts2 framework. It was developed with the specific intention of improving developer productivity and code simplicity. WebWork is built on top of XWork, which provides a generic command pattern framework as well as an Inversion of Control container.

WebWork provides robust support for building reusable UI templates, such as form controls, UI themes, internationalization, dynamic form parameter mapping to JavaBeans, robust client and server side validation, etc.


Design goals and overview

In a standard Java EE web application, the client will typically submit information to the server via a web form. The information is then either handed over to a Java Servlet which processes it, interacts with a database and produces an HTML-formatted response, or it is given to a JavaServer Pages (JSP) document which intermingles HTML and Java code to achieve the same result. Both approaches are often considered inadequate for large projects because they mix application logic with presentation and make maintenance difficult.

WebWork distinguishes itself by having understood existing frameworks' limitations and working to eliminate them. It supports type conversion, continuations, and interceptors. WebWork also supports multiple-view technologies like JSP, velocity, and FreeMarker.

Ultimately, WebWork has been designed and implemented with a specific set of goals, that are very important for its users. They are as follows:

  1. Web Designer never has to touch Java code
  2. Create multiple "Web Skins" for an application
  3. Change Look and Feel
  4. Change Layout on a given Web Page
  5. Change Flow among Web Pages
  6. Move *existing* data elements from one page to another
  7. Integrate with various backend infrastructures
  8. Reuse components
  9. Perform internationalization (i18n) of a web application
  10. Keep the API small and to the point
  11. Ability to learn WebWork fast, by making all the fancier features optional
  12. Allow the developer to choose how to implement as much as possible, while providing default implementations that work well in most cases [1]

WebWork lifecycle

The architecture of WebWork is based on the MVC, Command, and Dispatcher patterns and the principle of Inversion of Control. The life cycle of a WebWork request begins when the servlet container receives a new request. The new request is passed through a set of filters called the filter chain and sent to the FilterDispatcher. The FilterDispatcher forwards the request to the ActionMapper to determine what needs to be done with the request. If the request requires an action, it sends an ActionMapping object back to the FilterDispatcher. If not, ActionMapper returns a null object-which indicating that no action needs be taken. The FilterDispatcher forwards the request and the ActionMapper object to the ActionProxy for further action. The ActionProxy invokes the Configuration File manager to get the attributes of the action, which is stored in the xwork.xml file and creates an ActionInvocation object. The ActionInvocation object contains attributes like the action, invocation context, result, result code, etc. The configuration file manager has access to these configuration files and is used by the ActionProxy as a gateway to the configuration files. The ActionInvocation object also has information about Interceptors that need to be invoked after or before an action is executed.

ActionInvocation invokes all the interceptors listed in the ActionInvocation object and then invokes the actual action. When the action is completed, ActionInvocation gets the action result code from the execution. It uses the action result code to lookup the appropriate result, which is usually a JSP page, a velocity template or a freemarker template associated with the result code. ActionInvocation also executes the interceptors again in the reverse order and returns the response as a HttpServletResponse. [2]

WebWork / Struts merger

On November 27th, 2005, WebWork developer Patrick Lightbody announced that WebWork would be merging in to Struts2. [3] While the next major release (WebWork 2.2.x) was released under the WebWork name, all future major revisions (namely, 2.3.x and beyond) would be folded into Struts2.

Ted Husted, developer of Struts admitted in an email that WebWork is very similar to Struts 1.x and in fact does certain things better than Struts. Both Husted and Lightbody's rationale was that combining WebWork's superior technology and Struts' superior community could only have a good effect on the Java community as a whole.


WebWork uses the OpenSymphony Software License which is a modified (and fully compatible with) Apache Software License.

See also

External links

Got something to say? Make a comment.
Your name
Your email address