JSPs have dynamic scripting capability that works in tandem with HTML code, separating the page logic from the static elements — the actual design and display of the page — to help make the HTML more functional(i.e. dynamic database queries).
A JSP is translated into Java servlet before being run, and it processes HTTP requests and generates responses like any servlet. However, JSP technology provides a more convenient way to code a servlet. Translation occurs the first time the application is run. A JSP translator is triggered by the .jsp file name extension in a URL. JSPs are fully interoperable with servlets. You can include output from a servlet or forward the output to a servlet, and a servlet can include output from a JSP or forward output to a JSP.
JSPs are not restricted to any specific platform or server. It was orignially created as an alternative to Microsoft’s ASPs (Active Server Pages). Recently, however, Microsoft has countered JSP technology with its own ASP.NET, part of the .NETinitiative.
(Thanks go to William Duran at Oracle and the Oracle Technology Network for providing additional information for this definition.)