JavaServer Faces Application

Creating a Simple JavaServer Faces Application

JavaServer Faces technology provides an easy and user-friendly process for creating web applications. Developing a simple JavaServer Faces application typically requires the following tasks:

Developing managed beans
Creating web pages using component tags
Mapping the javax.faces.webapp.FacesServlet instance

This section describes those tasks through the process of creating a simple JavaServer Faces Facelets application.

The example is a Hello application that includes a managed bean and a web page. When accessed by a client, the web page prints out a Hello World message. The tasks involved in developing this application can be examined by looking at the application components in detail.

Developing the Managed Bean

A managed bean is a lightweight container-managed object. Components in a page are associated with managed beans that provide application logic. The example managed bean, Hello.java, contains the following code:

package hello;

import javax.faces.bean.ManagedBean;

@ManagedBean
public class Hello {

    final String world = "Hello World!";

    public String getworld() {
        return world;
    }
}

The example managed bean sets the value of the variable world with the string "Hello World!". The @ManagedBean annotation registers the managed bean as a resource with the JavaServer Faces implementation. For more information on managed beans and annotations

Creating the Web Page

In a typical Facelets application, web pages are created in XHTML. The example web page, beanhello.xhtml, is a simple XHTML page. It has the following content:

<html lang="en"
      xmlns="http://www.w3.org/1999/xhtml"
      xmlns:h="http://java.sun.com/jsf/html">
    <h:head>
        <title>Facelets Hello World</title>
    </h:head>
    <h:body>
        #{hello.world}
    </h:body>
</html>

A Facelets XHTML web page can also contain several other elements, which are covered later in this tutorial.

The web page connects to the managed bean through the Expression Language (EL) value expression #{hello.world}, which retrieves the value of the world property from the managed bean Hello. Note the use of hello to reference the managed bean Hello. If no name is specified in the @ManagedBean annotation, the managed bean is always accessed with the first letter of the class name in lowercase.

For more information on using EL expressions

Mapping the `FacesServlet` Instance

The final task requires mapping the FacesServlet, which is done through the web deployment descriptor (web.xml). A typical mapping of FacesServlet is as follows:

<servlet>
    <servlet-name>Faces Servlet</servlet-name>
    <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
    <servlet-name>Faces Servlet</servlet-name>
    <url-pattern>/faces/*</url-pattern>
</servlet-mapping>

The preceding file segment represents part of a typical JavaServer Faces web deployment descriptor. The web deployment descriptor can also contain other content relevant to a JavaServer Faces application configuration, but that information is not covered here.

The Lifecycle of the `hello` Application

Every web application has a lifecycle. Common tasks, such as handling incoming requests, decoding parameters, modifying and saving state, and rendering web pages to the browser, are all performed during a web application lifecycle. Some web application frameworks hide the details of the lifecycle from you, whereas others require you to manage them manually.

By default, JavaServer Faces automatically handles most of the lifecycle actions for you. However, it also exposes the various stages of the request lifecycle, so that you can modify or perform different actions if your application requirements warrant it.

It is not necessary for the beginning user to understand the lifecycle of a JavaServer Faces application, but the information can be useful for creating more complex applications.

The lifecycle of a JavaServer Faces application starts and ends with the following activity: The client makes a request for the web page, and the server responds with the page. The lifecycle consists of two main phases: execute and render.

During the execute phase, several actions can take place:

The application view is built or restored.
The request parameter values are applied.
Conversions and validations are performed for component values.
Managed beans are updated with component values.
Application logic is invoked.

For a first (initial) request, only the view is built. For subsequent (postback) requests, some or all of the other actions can take place.

In the render phase, the requested view is rendered as a response to the client. Rendering is typically the process of generating output, such as HTML or XHTML, that can be read by the client, usually a browser.

The following short description of the example JavaServer Faces application passing through its lifecycle summarizes the activity that takes place behind the scenes.

The hello example application goes through the following stages when it is deployed on the GlassFish Server.

When the hello application is built and deployed on the GlassFish Server, the application is in an uninitiated state.
When a client makes an initial request for the beanhello.xhtml web page, the hello Facelets application is compiled.
The compiled Facelets application is executed, and a new component tree is constructed for the hello application and is placed in a javax.faces.context.FacesContext.
The component tree is populated with the component and the managed bean property associated with it, represented by the EL expression hello.world.
A new view is built, based on the component tree.
The view is rendered to the requesting client as a response.
The component tree is destroyed automatically.
On subsequent (postback) requests, the component tree is rebuilt, and the saved state is applied.

Ref: http://docs.oracle.com/javaee/6/tutorial/doc/gjaam.html

Search This Blog

Techie Madness