Introduction
This article explores the Struts framework in depth and highlights the benefits Struts can
bring to your development efforts. We believe that once you can “talk the talk” of web
architecture and design, you will be better equipped to use Struts with your own
applications.
With a sound overview of the Struts architecture in place, we outline the Struts control
flow and the way it handles the request-response event cycle. A good understanding of
this process makes it much easier to create applications that make the best use of the
framework.
Choosing a web application framework should not be a casual decision. Many people will
use this book, and especially this chapter, as part of evaluating Struts for their project.
Accordingly, we conclude this chapter with a candid look at the strengths and weaknesses
of the Struts framework and address concerns regarding overall performance. Struts is
designed for professional developers. To make informed decisions, professionals need to
be aware of both a tool’s capabilities and its limitations.
A Greatt Desiign Pattttern – MVC
Part of MVC triad
A Model in MVC terms is a presentation-neutral arbiter of data. This data then can be
tailored to support a given presentation, or tailored to represent application-specific data
structures.
A View is a presentation-specific way of displaying data from a Model. There is a
relationship between a Model and View such that changes in a Model are automatically
reflected in any Views attached to it, and changes in the View-presented data are
automatically pushed back to associated Models.
The controller coordinates activity Model and View, and for the application as a whole.
Whereas Model and View can frequently be instances of off-the-shelf types, Controllers
are typically custom written to an application.
Fig 1, below depicts MVC design pattern. Here all different types of flows have been
depicted, which whenever separated can lead to different implementations of MVC.
|
