Apache Struts MVC Design Pattern
A sample from
Beginning Apache Struts: From Novice to Professional
by Arnold Doray
Servlet technology is the primary base on which you can create web applications with Java. JavaServer Pages
(JSP) technology is based on servlet technology but extends it by allowing HTML content to be created easily.
Note that JSP technology doesn’t replace servlet technology, but rather builds on it, to address some of its
deficiencies. Struts follows this pattern, and builds on servlet and JSP technologies to address their shortcomings. These shortcomings are
in two broad areas:
Creating a “separation of concerns”: Pieces of code that do different things are bundled separately and given standardized
ways of communicating between themselves.
An infrastructure for webapps: This includes things like validating user input, handling and reporting errors, and managing flow
control.
If these shortcomings are addressed, the very practical problems of building webapps (robustness, maintainability, localization, etc.)
become easier to tackle.
One tool that can be used to make some headway in resolving these issues is an organizing principle
called the Model-View-Controller (MVC) design pattern.
WHAT ARE DESIGN PATTERNS?
Design patterns are essentially recipes for solving generic coding problems. They are not algorithms but rather organizational principles for
software.
The idea of using “design patterns” to solve common software engineering problems first came to prominence with the book Design
Patterns: Elements of Reusable Object-Oriented Software (Addison-Wesley Professional, 1995), by, by Erich Gamma, Richard Helm, Ralph
剩余16页未读，继续阅读
资源评论
