Definitions

1. A JSP container is an entity that translates, executes, and processes JSP pages and delivers requests to them.
2. A JSP Container is a middleware library, that is able to translate JSP pages into HTML. (Web site)
3. The JSP container is responsible for intercepting requests for JSP pages and processes these requests in order to provide the JSP pages to the requester. (Web site)
4. The JSP container is often implemented as a servlet configured to handle all requests for JSP pages. (Web site)
5. The JSP container is provided as a component of OC4J but is portable to other environments. (Web site)

Jsp Page Implementation

1. During the execution phase the JSP container delivers events to the JSP page implementation object.

El Expressions

1. From the Faces perspective, any EL expressions that appear in a JSP page are parsed by the JSP container. (Web site)

Oc4J

1. The JSP container in OC4J uses the front-end servlet oracle.jsp.runtimev2.JspServlet. (Web site)

Oracle Jsp Container

1. It also includes a JSP 1.1 reference implementation, but you can use the Oracle JSP container on top of it. (Web site)

Version

1. Version 1.1.2.4 of the Oracle JSP container is supplied with Oracle9 i release 2.

Subject

1. The included file is subject to the access control available to the JSP container. (Web site)

Means

1. The default value is true, which means that the JSP container can send multiple, concurrent client requests to the JSP page. (Web site)

Oc4J Jsp Container

1. Because of this extended functionality, the OC4J JSP container is not limited by the underlying servlet environment. (Web site)

Overview

1. The OC4J JSP container supports this feature, as described in the previous section, "Overview of a Custom Tag Library Implementation". (Web site)
2. For further overview of the JSP container provided with OC4J, see "Overview of the JSP Implementation in OC4J". (Web site)

Empty

1. This tells the JSP container that the body content must be empty rather than containing any JSP syntax to be parsed.

First Time

1. The JSP container locates the JSP page and translates it if this is the first time it has been requested.

Environment

1. The JSP container also supports tag handler reuse in a servlet 2.0 environment. (Web site)
2. Special considerations in using the Oracle JSP container with a servlet 2.0 environment are discussed in Chapter 9, "Oracle JSP in Apache JServ". (Web site)

Objects

1. These are Java objects that are created automatically by the JSP container and that allow interaction with the underlying servlet environment. (Web site)

Messages

1. JSP.2.10 Directives Directives are messages to the JSP container.

Message

1. By default, the JSP container catches the exception and displays its message and stack trace in the browser, similar to what's shown in Figure 9-1.

Set

1. The pageContext is set by the JSP container and is available to the Tag Handler. (Web site)

First

1. First and foremost, Facelets isn't dependent on a JSP container. (Web site)

Method

1. When you use the beanName attribute, the JSP container creates the instance by using the instantiate() method of the java.beans.Beans class. (Web site)
2. The JSP container automatically generates this method, based on the contents of the JSP page. (Web site)
3. This method is defined automatically by the JSP container and should NEVER be defined by the JSP page author. (Web site)

Specification

1. The Oracle JSP container, however, offers functionality that emulates the application support provided with the servlet 2.1(b) specification. (Web site)

Process

1. The JSP container needs every JSP element to be written exactly as it's defined in the specification in order to process the JSP page.

Processes

1. The JSP container processes the page and invokes the JSF action tag handlers as they are encountered.
2. The <c:forEach is evaluated by the JSP container (outside of the control of JSF) every time it processes the JSP page.

Action

1. When the include action is finished, the JSP container continues processing the remainder of the JSP file. (Web site)
2. When the include action is finished, the JSP container continues processing the remainder of the JSP page. (Web site)

Tag

1. A JSP container uses the TLD file in determining what action to take when it encounters a tag from the library.
2. JSP: meaning that the JSP container should evaluate any body of the tag, but it can also be empty.
3. Methods you code that describe the actions that occur when the JSP container encounters your tag should return the appropriate constant.

Output

1. Note that the JSP container will not interpret anything provided by jsp:output.
2. This source text results in the following output from the OC4J JSP container. (Web site)

Xml Declaration

1. It means that if the JSP container is generating an XML declaration, this is what the JSP container will include in the output of your JSP document.

Javaserver Pages

1. JavaServer Pages (JSP) Directive page include Description Defines page settings for the JSP container to process. (Web site)

Servlet Container

1. The application scope ends when the application itself terminates, or when the JSP container or servlet container shuts down. (Web site)
2. This includes the JSP container described in this manual, a servlet container, and an EJB container. (Web site)

Translation Time

1. JSP directive A JSP element that gives an instruction to the JSP container and is interpreted at translation time.

Jsp Comments

1. JSP Comments A comment marks text or lines that the JSP container should ignore. (Web site)

Servlet Class

1. The server with the JSP container may then execute the servlet class to return the requested JSP content to the client computing device. (Web site)

Jsp Page Implementation Class

1. The JSP container creates a JSP page implementation class for each JSP page. (Web site)

Xml Document

1. Beginning with JSP 1.2, the XML document can be delivered to a JSP container for processing.

Entire Page

1. JSP directives are as a message from a JSP page to the JSP container that control the processing of the entire page.

Jsp Pages

1. JSP pages should have the file extension.jsp, which tells the server that the page needs to be processed by the JSP container. (Web site)

Template Text

1. The JSP container doesn't care what the template text is.

Mime Type

1. You can use any MIME type or character set that are valid for the JSP container. (Web site)

Oracle Application

1. The JSP container in Oracle Application Server 10 g Release 2 (10.1.2) is compliant with the JSP 1.2 specification. (Web site)
2. In Oracle Application Server 10 g Release 2 (10.1.2), the OC4J JSP container by default expects JSP 1.1, not JSP 1.2, tag syntax and usage. (Web site)

Attributes

1. If one is specified, then it is instantiated by the JSP container and its isValid() method is called to validate the attributes of the tag. (Web site)
2. It defines a number of page dependent attributes and communicates these attributes to the JSP container.

Page Directive

1. JSP.2.10.1 The page Directive The page directive defines a number of page dependent properties and communicates these to the JSP container.
2. The page directive defines a number of page dependent properties and communicates these to the JSP container. (Web site)
3. An example of a page directive is one that tells the JSP container to load an error page when it throws an exception.

Web

1. Upon noting the.jsp file name extension in the URL, the servlet container of the Web server invokes the JSP container.
2. The Web server must first interpret the JSP page to generate the dynamic page content, this process is performed by the JSP container. (Web site)
3. The OC4J JSP container enables XML validation of TLD files separately from validation of the web.xml file. (Web site)

Front-End

1. This servlet can be thought of as the front-end of the JSP container.
2. This servlet can be thought of as the front-end of the Oracle JSP container. (Web site)

Implementation

1. In the OC4J 10.1.2 implementation, the OC4J JSP container is fully compliant with the JSP 1.2 specification. (Web site)

Web Container

1. A Web container provides the same services as a JSP container as well as a federated view of the J2EE platform APIs.

Page

1. The first time the end-user requests HelloWorld.jsp, the JSP container triggers both translation and execution of the page.
2. Before you use a bean in a page, you must tell the JSP container which type of bean it is and associate it with a name.
3. The OC4J JSP container generates an XML view of every translated page, which is a mapping to an XML document that describes the page.

Request

1. If the container handling the request is a JSP container, a URL containing a.jsp extension is implicitly mapped.
2. Scriptlets are executed at request time, when the JSP container processes the request. (Web site)

Requests

1. Requests sent to a JSP page are delivered by the JSP container to the appropriate JSP page implementation object.
2. The translation may also be done by the JSP container at deployment time, or on-demand as the requests reach an untranslated JSP page.

Categories

1. Jsp Page
2. Servlet Container
3. Tld
4. Web Container
5. Tag Library

Related Keywords

* Container * Directive * Directives * Jsp * Jsps * Jsp Page * Jsp Specification * Servlet * Servlets * Taglib Directive * Tag Libraries * Tag Library * Tld

1. Books about "Jsp Container" in Amazon.com
   

Continue: More Keywords - - - - - - - - - -