Java Server Pages Technology

JSP technology is implemented as a Java API; the JSP API is part of the Java 2 Platform, Enterprise Edition (J2EE). Because pages created with JSP actually compile into servlets, they build on and extend the Servlet API as well. Because JSP technology as part of the J2EE platform, expect to see more servers and tools supporting this API.

The Java Server Pages architecture enables the separation of content generation from content presentation. This separation not only eases maintenance headaches, it also allows web team members to focus on their areas of expertise. Now, webpage designers can concentrate on layout, and web application designers on programming, with minimal concern about impacting each other's work.

The important features of JSP can be classified as:

Portability
Composition
Processing

Java Server Pages files can be run on any web server or web-enabled application server that provides support for them. Dubbed the JSP engine, this support involves recognition, translation, and management of the JavaServer Page lifecycle and its interactions with associated components.

The JSP engine for a particular server might be built-in or might be provided through a 3rd-party add-on. As long as the server on which you plan to execute the JavaServer Pages supports the same specification level as that to which the file was written, no changes should be necessary as you move your files from server to server. Note, however, that instructions for the setup And configuration of the files may differ between f i les.

To date, there has been no upwards- or backwards-compatibility between JavaServer Pages specifications. A JavaServer Pages file written to the 0.92 specification can be run only on a server supporting JavaServer Pages 0.92. The same file could not run on a server supporting only JavaServer Pages 1.0 or JavaServer Pages 0.91.

it was mentioned earlier that the JavaServer Pages architecture could include reusable Java components. The architecture also allows for the embedding of a scripting language directly into the JavaServer Pages file.

The components that are currently supported include JavaBeans, and Servlets. Support for Enterprise Java Beans components is likely to be added in a future release. As the default scripting language, JavaServer Pages use the Java programming language. This means that scripting on the server side can take advantage of the full set of capabilities that the Java programming language offers. Support for other scripting languages might become available in the future.

A Java Server Pages file is essentially an HTML document with JSP scripting or tags. It may have associated components in the form of class, Jar, or ser files. The use of components is not required.

The JavaServer Pages file has a jsp extension to identify it to the server as a JavaServer Pages file. Before the page is served, the JavaServer Pages syntax is parsed and processed into a servIet on the server side. The servIet that is generated outputs real content in straight HTML for responding to the client. Because it is standard HTML, the dynamically generated response looks no different to the client browser than a static response.

Domain Name Search