Introduction to WebLogic htmlKona

 

Deprecation of WebLogic htmlKona

WebLogic htmlKona is deprecated in this release of WebLogic Server 6.0. For support for your JSPs, use WebLogic JavaServer Pages (JSP). For more information on JSPs, see Programming WebLogic JSP.

The following sections provide an overview of WebLogic htmlKona and an explanation of how to use JSP with WebLogic Server. It is not intended as a comprehensive guide to programming with JSP.

• What Is htmlKona?

• WebLogic Implementation of JSP

• How JSP Requests Are Handled

• Additional Information

What Is htmlKona?

JavaServer Pages (JSP) is a Sun Microsystems specification for combining Java with HTML to provide dynamic content for Web pages. When you are creating dynamic content, JSPs are more convenient to write than HTTP servlets because they allow you to embed Java code directly into your HTML pages, in contrast with HTTP servlets, in which you embed HTML inside Java code. JSP is part of the Java Two Enterprise Edition (J2EE).

JSP allows you to separate the dynamic content of a Web page from its presentation. It caters to two different types of developers: HTML developers, who are responsible for the graphical design of the page, and Java developers, who handle the development of software to create the dynamic content.

Because JSP is part of the J2EE standard, JSPs may be deployed on a variety of platforms, including WebLogic Server. In addition, third-party vendors and application developers can provide JavaBean components and define custom JSP tags that can be referenced from a JSP page to provide dynamic content.

WebLogic Implementation of JSP

BEA WebLogic JSP supports the JSP 1.1 specification from Sun Microsystems. JSP 1.1 includes support for defining custom JSP tag extensions. (See Programming JSP Extensions)

WebLogic Server also supports the Servlet 2.2 specification from Sun Microsystems.

How JSP Requests Are Handled

WebLogic Server handles JSP requests in the following sequence:

1. A browser requests a page with a .jsp file extension from WebLogic Server.

2. WebLogic Server reads the request.

3. WebLogic Server converts the JSP into a servlet class that implements javax.servlet.jsp.JspPage using the JSP compiler. The JSP file is compiled only when the page is first requested, or when the JSP file has been changed. Otherwise, the previously compiled JSP servlet class is re-used, making subsequent responses much quicker.

4. The generated JspPage servlet class is invoked to handle the browser request.

It is also possible to invoke the JSP compiler directly without making a request from a browser. Because the JSP compiler creates a Java servlet as its first step, you can look at the Java files it produces, or even register the generated JspPage servlet class as an HTTP servlet.

Additional Information

• JavaServer Pages Tutorial from Sun Microsystems

• JSP product overview from Sun Microsystems

• JSP 1.1 Specification from Sun Microsystems

• Programming JSP Extensions.

• Programming WebLogic HTTP Servlets.

• Deploying and Configuring Applications

• Writing Web Application Deployment Descriptors