Previous
The Problems with Model 1
The Model 1 design model is page-centric. Applications implementing this model have a series of JSPs where the user proceeds from one page to another. This is the model you always employ when you first learn JSP because it is simple and easy. The main problem with Model 1 applications is that they are hard to maintain and inflexible. On top of that, this architecture does not promote the division of labor between the page designer and the Web developer because the developer is involved in both page development and business logic coding.
To summarize, Model 1 is not recommended for the following reasons:
- Navigation problem. If you change the name of a JSP that is referenced by other pages, you must change the name in many locations.
- There is more temptation to use scriptlet in JSPs because JavaBeans are limited and it is relatively harder to write custom tags. However, as explained above, mixing Java code and HTML in JSP pages is a bad thing.
- If you can discipline yourself to not write Java code in JSPs, you end up spending more time developing your application because you have to write custom tags for most of your business logic. It is faster to write Java code in normal Java classes.