"WebWork is an open source Web development framework for building Model 2 applications. Philosophically, it is closer to Struts than Tapestry. It works within the existing Web APIs in Java rather than attempting to replace them completely. WebWork contains several concepts and constructs that are unique and that set it apart from other frameworks, such as the Pull Hierarchical Model-View-Controller design and the value stack, which supplies values to their custom JSP (Java Server Pages) tags. We begin with a history and background of the framework. We then explore some key concepts and constructs that are vital when you're working with the framework. As always, the principles of Model 2 development provide the guidelines for the samples and dictate a firm separation of concerns."
"WebWork in Action is a book that walks through the WebWork framework, beginning with the basics of using WebWork continuing all the way through the interceptor and component models of WebWork. This introductory walkthrough of WebWork exposes you to the core ideas behind WebWork, providing a basis for diving further into the capabilities of the framework. With WebWork being accepted into the Struts family as Struts Ti, chances are that many developers will be able to use this information as a quick step into a future version of Struts."
"OpenSymphony's WebWork is a web application framework designed to keep productivity high and the code simple. It has gained popularity for several reasons, including its integration with Spring, a powerful tag library, and OGNL support. Its powerful validation framework is borrowed from another OpenSymphony project, XWork."
"There is one particular aspect of Groovy that really caught my attention at Rod's talk : the Java language is (99%) a sub-set of Groovy. Rod explained that there are still a few Java language features that aren't part of Groovy yet, but the Groovy evangelists don't seem to miss them. But basically 99% of the time you can take a .java, rename it .groovy, run it through the groovy interpreter and get expected results."
"Specifically I'm looking at the multiple ways in which you can use spring-managed beans from webwork actions. The best document I could find on it is here, which got me started but also left me a little confused."
"WebWork is a Model-View-Controlled type of framework. This means it separates logic from view and simplifies Web development by using a powerful "action" concept on the server side."
