Chapter 7. Developing Web Applications Using the Model 1 Architecture

Look into any web application, and you should recognize the presence of some web navigation scheme that dictates how pages should flow along with the data that needs to be processed with them. Some applications employ Model 1 Architecture practices that hard code these flows in the pages that comprise their web applications, whereas others use Model 2 practices that embed flow attributes in an external file so that maintenance and navigation paths can be handled outside the code itself. Inevitably, speculations during the design phase of your program will have to be made as to which method will be put into practice prior to software deployment. Outside influences, like experimentation and lessons learned from previous engagements ("been there, done that, got the T-shirt"), could be used in your decision making, but more likely, delivery timelines, staff maturity, and scheduling constraints will affect this decision.

This chapter demonstrates how you can overcome speculation over how to construct a web application using the Model 1 Architecture by constructing a hands-on Contact Management Tool. Two different types of Java syntax, JSTL 1.1 and JSP 2.0, will be utilized to craft the sample GUI component that will allow users to manage contact information through upload and query activities. The sample application's use of Model 1 was chosen to suit design and implementation needs for a quick prototype that can be ...

Get Professional Java® JDK®, 6th Edition now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.