A container that implements the Web component contract of the J2EE architecture. This contract specifies a runtime environment for Web components that includes security, concurrency, life-cycle management, transaction, deployment, and other services. A Web container provides the same services as a JSP container as well as a federated view of the J2EE platform APIs. A Web container is provided by a Web or J2EE server.

A set of phases during which a request for a page is received, a UI component tree representing the page is processed, and a response is produced. During the phases of the life cycle:

The local data of the components is updated with the values contained in the request parameters.

Events generated by the components are processed.

Validators and converters registered on the components are processed.

The components' local data is updated to back-end objects.

The response is rendered to the client while the component state of the response is saved on the server for future requests.

A file containing the keys and certificates used for authentication. What is life cycle (J2EE component)

The framework events of a J2EE component's existence. Each type of component has defining events that mark its transition into states in which it has varying availability for use. For example, a servlet is created and has its init method called by its container before invocation of its service method by clients or other servlets that require its functionality. After the call of its init method, it has the data and readiness for its intended use. The servlet's destroy method is called by its container before the ending of its existence so that processing associated with winding up can be done and resources can be released. The init and destroy methods in this example are callback methods. Similar considerations apply to the life cycle of all J2EE component types: enterprise beans, Web components (servlets or JSP pages), applets, and application clients.

We encounter cycle stealing in the context of Direct Memory Access (DMA). Either the DMA controller can use the data bus when the CPU does not need it, or it may force the CPU to temporarily suspend operation. The latter technique is called cycle stealing. Note that cycle stealing can be done only at specific break points in an instruction cycle.

An object that provides the life-cycle operations (create, remove, find) for an enterprise bean. The class for the EJB home

object is generated by the container's deployment tools. The EJB home object implements the enterprise bean's home interface.

The client references an EJB home object to perform life-cycle operations on an EJB object. The client uses JNDI to locate an

EJB home object.

A container that implements the EJB component contract of the J2EE architecture. This contract specifies a runtime

environment for enterprise beans that includes security, concurrency, life-cycle management, transactions, deployment,

naming, and other services. An EJB container is provided by an EJB or J2EE server. What is EJB container provider

A vendor that supplies an EJB container.

The contract between a J2EE component and its container. The contract includes life-cycle management of the component, a

context interface that the instance uses to obtain various information and services from its container, and a list of

services that every container must provide for its components.

Component methods called by the container to notify the component of important events in its life cycle.

The Mobile Information Device Profile (MIDP) is a specification for a J2ME profile. It is layered on top of CLDC and adds APIs for application life cycle, user interface, networking, and persistent storage.

The Foundation Profile is a J2ME profile specification that builds on CDC. It adds additional classes and interfaces to the CDC APIs but does not go so far as to specify user interface APIs, persistent storage, or application life cycle. Other J2ME profiles build on the CDC/Foundation combination: for example, the Personal Profile and the RMI Profile both build on the Foundation Profile.