Summary

JSPs are intended to separate content from presentation. They are conceptually very similar to servlets. JSPs are essentially similar to a server-side scripting technology, the key difference being that JSPs are compiled, whereas scripts are interpreted.

Although a JSP is equivalent to a servlet, a JSP is not intended as a replacement for a servlet. Two development paradigms, generally referred to as Model 1 and Model 2, provide the underpinnings for effective use of servlets and JSPs.

A JSP consists of Java code embedded within a structured document such as HTML or XML. Tags are used to mark up specific pieces of JSP code. Users can also create their own tag libraries in the form of taglib libraries.

In the UML, JSPs and associated technology relationships are modeled by stereotyping existing UML constructs. A JSP is modeled as being composed of two distinct conceptual elements: the client page and the server page. The relationship between the client page and the server page is modeled as a build relationship. Client and server pages can also have relationships with other client and server pages.