Classification of Design Pattern in Software Development

Classification of  Software Design Pattern		Purpose [reflects what a pattern does]
		Creational [concern the process of object creation]	Structural [deal with the composition of classes or objects]	Behavioral [characterize the ways in which classes or objects interact and distribute responsibility]
Scope [specifies whether the pattern applies primarily to classes or to objects]	Class [deal with relationships between classes and their subclasses. These relationships are established through inheritance, so they are static—fixed at compile-time ]	Factory Method [Class-creational patterns deal with Class-instantiation. They defer their object creation to subclasses.]	Adapter [The Structural class patterns use inheritance to compose classes]	Interpreter Template Method [Behavioral class patterns use inheritance to describe algorithms and flow of control]
	Object [Object patterns deal with object relationships, which can be changed at run-time and are more dynamic]	Abstract Factory Builder Prototype Singleton [Object-creational patterns deal with Object creation. They defer the part of their object creation to another object]	Adapter Bridge Composite Decorator Facade Flyweight Proxy [the Structural object patterns describe ways to assemble objects]	Chain of Responsibility Command Iterator Mediator Memento Observer State Strategy Visitor [the Behavioral object patterns describe how a group of objects cooperate to perform a task that no single object can carry out alone]

Struts Framwork for Netbeans

The Struts Framework is a standard for developing well-architected Web applications. It has the following features:

* Open source
* Based on the Model-View-Controller (MVC) design paradigm, distinctly separating all three levels:
o Model: application state
o View: presentation of data (JSP, HTML)
o Controller: routing of the application flow
* Implements the JSP Model 2 Architecture
* Stores application routing information and request mapping in a single core file, struts-config.xml

The Struts Framework, itself, only fills in the View and Controller layers. The Model layer is left to the developer.



Another Workflow...Collected from sruts for netbeans





Struts Components

The Controller

This receives all incoming requests. Its primary function is the mapping of a request URI to an action class selecting the proper application module. It's provided by the framework.


The struts-config.xml File
This file contains all of the routing and configuration information for the Struts application. This XML file needs to be in the WEB-INF directory of the application.


Action Classes
It's the developer's responsibility to create these classes. They act as bridges between user-invoked URIs and business services. Actions process a request and return an ActionForward object that identifies the next component to invoke. They're part of the Controller layer, not the Model layer.


View Resources
View resources consist of Java Server Pages, HTML pages, JavaScript and Stylesheet files, Resource bundles, JavaBeans, and Struts JSP tags.


ActionForms
These greatly simplify user form validation by capturing user data from the HTTP request. They act as a "firewall" between forms (Web pages) and the application (actions). These components allow the validation of user input before proceeding to an Action. If the input is invalid, a page with an error can be displayed.


Model Components
The Struts Framework has no built-in support for the Model layer. It enables you to create maintainable, extensible, and flexible web applications based on standard technologies, such as JSP pages, JavaBeans, resource bundles, and XML.