Java Tutorial - Java Script :
Architectural Considerations
In the Java community, the MVC design pattern is widely recognized as the way to go for developing medium to large-scale enterprise Web applications. The MVC design pattern is associated with the JSP Model 2 development approach. In JSP Model 2 development, the JavaServer Page is used strictly to render the output of a Web page. A servlet is used to act as a controller, determining which page to generate and gathering the information to be rendered into HTML by the JSP. Someone just being introduced to application frameworks will naturally want to know answers to questions such as, “What does a framework do for me?” and “Why should I want to use it?” The answer to these questions, as we shall see, is that this approach speeds up the development process and helps in the creation of higher-quality and easier-to-maintain software. After the MVC design architecture became a de facto standard, it became clear after its repeated use on application after application that there were similar activities being performed within each of these applications. A Web browser normally issues a request to a servlet; the servlet instantiates a Java- Bean that encapsulates the business logic and data, which in turn will be handed over to the JSP for presentation back to the browser. Any time a pattern or repeatable series of events can be identified, there is usually a way to construct a device or mechanism with which to automate a process. The realization of this automation for Web application development manifests itself as a Web application framework.
