Home » Enterprise Java » jsf » JSF Event Queue Example

About Yatin

An experience full-stack engineer well versed with Core Java, Spring/Springboot, MVC, Security, AOP, Frontend (Angular & React), and cloud technologies (such as AWS, GCP, Jenkins, Docker, K8).

JSF Event Queue Example

Hello, in this tutorial we will study about Event Queue listener in a jsf enabled application and will demonstrate the following:

  • Validating the user’s role in current session
  • Access Denied page in case of an error

This example will show the integration and implementation of event queue listener.

1. Introduction

The model that JSF implements for handling Events is based on the standards defined in Java Beans Specification. JSF user interface components are sources that can emit some kind of signals based on the user actions. These signals are often termed as Events. Applications who want to process the Events can attach any number of Event Listeners to Event Sources.

JSF provides system event listeners to perform application specific tasks during JSF Application Life Cycle, for e.g.

System EventDescription
PostConstructApplicationEventFires when the application starts. Can be used to perform initialization tasks after the application has started
PreDestroyApplicationEventFires when the application is about to shut down. Can be used to perform cleanup tasks before the application is about to shut down
PreRenderViewEventFires before a JSF page is to be displayed. Can be used to authenticate the user and provide restricted access to JSF View


In the below tutorial, we will have the following components:

  • default.xhtml – A jsf page to which PreRenderViewEvent is attached
  • not-admin-user.xhtml – A jsf page to deny the user’s access if he or she is not an administrator
  • UserBean – Managed bean class to validate user’s role in the current session
  • web.xml – Web application configuration file

But before we create the application let’s take a look at the EventQueue listener in jsf.

1.1 Event Queue Listener

When the user clicks a button or link, changes a value in a field or makes a selection in a list the application may need to react. JSF user interface components signal user actions by firing an event handled by application code that has registered itself to be notified of the event. It’s a model borrowed from traditional GUI frameworks, making it easy to develop and maintain the code for each specific user action in a separate code module.

In this tutorial, we will be attaching a javax.faces.event.PreRenderViewEvent system event to perform a custom task before a view root (JSF page) is displayed.

1.2 Why is Event Queue Listener needed?

We may have a requirement to perform a custom task before a view root page is displayed i.e. creating a database connection pool and initializing database connections during the application startup or we would like to know how many sessions were created in an application before the application is about to shut-down.

1.3 How it can be achieved?

Servlet programmers can handle the event queue operations in the following manner:

SystemEventListenerImplement SystemEventListener interface and register the system-event-listener class in faces-config.xml
Method BindingPass the name of the managed bean method in listener attribute of f:event


In case developers want to briefly understand the SystemEventListener interface approach briefly, they might consider this option. Now, open up the Eclipse IDE and let’s start building the application!

2. JSF EventQueue Example

2.1 Tools Used

We are using Eclipse Kepler SR2, JDK 8 (1.8.0_131), Tomcat7 application server. Having said that, we have tested the code against JDK 1.7 and it works well.

2.2 Project Structure

Firstly, let’s review the final project structure, in case you are confused about where you should create the corresponding files or folder later!

Fig. 1: Jsf EventQueue Application Project Structure

Fig. 1: Jsf EventQueue Application Project Structure

2.3 Project Creation

The below example shows how to implement the event queue using a method binding technique in an application. This section will demonstrate on how to create a Dynamic Web Java project with Eclipse. In Eclipse IDE, go to File -> New -> Dynamic web project

Fig. 2: Create Dynamic Web Project

Fig. 2: Create Dynamic Web Project

In the New Dynamic Project window fill in the below details and click next

  • Enter the project name and project location
  • Select Target runtime as Apache Tomcat v7.0 from dropdown
  • Select Configuration as JavaServer Faces v.2.2 Project from dropdown (this is required to download the java server faces capabilities in your project)
Fig. 3: Project Details

Fig. 3: Project Details

Leave everything as default in this window as we will be making the required java file at a later stage. Simply click next and we will land up on the web-module window

Fig. 4: Java Src Window

Fig. 4: Java Src Window

In the Web Module window, leave the context_root and content_directory values as default (however, you can change the context_root but for the first application let’s keep it as a default value). Simply, check Generate web.xml deployment descriptor checkbox and click next

Fig. 5: Web Module Window

Fig. 5: Web Module Window

In the JSF Capabilities windows, we will require downloading the dependencies (not available by default) so that our project is configured as a JSF module in Eclipse. Add the JSF capabilities to the web project by clicking on the download icon (encircled in Fig. 6) and download the JSF 2.2 Mojarra implementation

Fig. 6: JSF Capabilities Window

Fig. 6: JSF Capabilities Window

A new pop-up window will open where it will auto lists down the JSF library. Select the JSF 2.2 library and click next (the library name and download destination will be auto populated)

Fig. 7: JSF Capabilities Download Window

Fig. 7: JSF Capabilities Download Window

Check the license checkbox and click finish. Eclipse will download the JSF 2.2 library and will display them on the JSF capabilities windows (i.e. Fig. 6)

Fig. 8: JSF Capabilities License Window

Fig. 8: JSF Capabilities License Window

Now the JSF implementation libraries will be listed down on the capabilities page. Select the checkbox (JSF2.2 (Mojarra 2.2.0)) and leave everything else as default. Click Finish

Fig. 9: JSF Capabilities Library Selection Window

Fig. 9: JSF Capabilities Library Selection Window

Eclipse will create the project named JSF EventQueue in the workspace and web.xml will be configured for accepting the JSF requests. It will have the following code:


<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" id="WebApp_ID" version="3.0">
    <display-name>JSF EventQueue</display-name>
        <servlet-name>Faces Servlet</servlet-name>
        <servlet-name>Faces Servlet</servlet-name>
        <description>State saving method: 'client' or 'server' (=default). See JSF Specification 2.5.2</description>

Let’s start building the application!

3. Application Building

Below are the steps involved in developing this application:

3.1 Source File Creation

For the demo, we will have an output file displaying the products list. Right click on project WebContent -> New -> File

Note: In JSF 2.0, it’s recommended to create a JSF page in xhtml format, a file format with .xhtml extension

Fig. 10: File Creation

Fig. 10: File Creation

A pop-up window will open. Verify the parent folder location as JSF EventQueue/WebContent and enter the file name as default.xhtml. Click Finish

Fig. 11: default.xhtml

Fig. 11: default.xhtml

Repeat the step listed in Fig. 10. Verify the parent folder location as JSF EventQueue/WebContent and enter the file name as not-admin-user.xhtml and click Finish

Fig. 12: not-admin-user.xhtml

Fig. 12: not-admin-user.xhtml

3.1.1 Implementation of Input & Output file

Here in the default.xhtml, we will use f:event tag to attach preRenderView to this page. Add the following code to it:


<html lang="en" xmlns="http://www.w3.org/1999/xhtml" 
    <meta charset="utf-8" name="viewport" content="width=device-width, initial-scale=1" http-equiv="X-UA-Conpatible" />
    <title>JSF EventQueue</title>
    <center><h2>JSF EventQueue Example</h2></center>
    <h:form id="userRoleForm">
    	<f:event listener="#{userBean.isAdmin}" type="preRenderView" />

Accessing default.xhtml page, the user will navigate to the error page in case the login requirements are not met. Add the following code to it:


<html lang="en" xmlns="http://www.w3.org/1999/xhtml" 
    <meta charset="utf-8" name="viewport" content="width=device-width, initial-scale=1" http-equiv="X-UA-Conpatible" />
    <title>JSF EventQueue</title>
    <style type="text/css">    
    	.errorMsg {
    		color: red;
    		padding-top: 16px; 
    	.row {
    		margin-left: 18px;
    <center><h2>JSF EventQueue Example</h2></center>
    <div class="container">
        <div class="row">
            <div class="form_bg">
            	Hello <h:outputText value="#{userBean.userName}" />
            	<div class="errorMsg">
            		<span>!! Sorry, you are not an authorized user. Access denied !!</span>            	

3.2 Java Class Creation

Let’s create the required java files. Right click on src folder New -> Package

Fig. 13: Java Package Creation

Fig. 13: Java Package Creation

A new pop window will open where we will enter the package name as com.jsf.event.queue

Fig. 14: Java Package Name (com.jsf.event.queue)

Fig. 14: Java Package Name (com.jsf.event.queue)

Once the package is created in the application, we will need to create the required managed bean. Right click on the newly create package New -> Class

Fig. 15: Java Class Creation

Fig. 15: Java Class Creation

A new pop window will open and enter the file name as UserBean. The managed bean class will be created inside the package com.jsf.event.queue

Fig. 16: Java Class (UserBean.java)

Fig. 16: Java Class (UserBean.java)

3.2.1 Implementation of Managed Bean

We will create a normal bean containing a method signature public void method-name(ComponentSystemEvent event). In this method, we will validate the role in the current session. If the role is not equal to Administrator, then the user will be navigated to an error page. Add the following code to it:


package com.jsf.event.queue;

import javax.faces.application.ConfigurableNavigationHandler;
import javax.faces.bean.ManagedBean;
import javax.faces.bean.SessionScoped;
import javax.faces.context.FacesContext;
import javax.faces.event.ComponentSystemEvent;

@ManagedBean @SessionScoped
public class UserBean {

	public String userName;

	public String getUserName() {
		return userName;

	public void setUserName(String userName) {
		this.userName = userName;

	// Method To Check Whether The User Request Has Administrator Role Or Not?
	public void isAdmin(ComponentSystemEvent event) {	
		String checkUserRole =  (String) FacesContext.getCurrentInstance().getExternalContext().getSessionMap().get("role");		
		boolean isUserRoleEmpty = checkUserRole == null || checkUserRole.trim().length() == 0;
		if (isUserRoleEmpty) {			
			userName = "Java Geek";
			ConfigurableNavigationHandler navigationObj = (ConfigurableNavigationHandler) FacesContext.getCurrentInstance().getApplication().getNavigationHandler();
		} else if((!isUserRoleEmpty) && checkUserRole.equalsIgnoreCase("Administrator")) {
			// Do Some Stuff If User Role Is Administrator
		} else {
			// Do Some Stuff If User Role Is Normal

4. Project Deploy

Once we are ready with all the changes done, let us compile and deploy the application on tomcat7 server. In order to deploy the application on tomcat7, right-click on the project and navigate to Run as -> Run on Server

Fig. 17: How to Deploy Application On Tomcat

Fig. 17: How to Deploy Application On Tomcat

Tomcat will deploy the application in its webapps folder and shall start it’s execution to deploy the project so that we can go ahead and test it on the browser

Fig. 18: Tomcat Processing

Fig. 18: Tomcat Processing

Open your favorite browser and hit the following url: http://localhost:8082/JSFEventQueue/faces/default.xhtml

Server name (localhost) and port (8082) may vary as per your tomcat configuration

5. Project Demo

Now, we are done with the application and it’s time to test out the application. Accessing this page (i.e. default.xhtml), having “role” value in the session object, will navigate the output to the access denied page (i.e. not-admin-user.xhtml)

Fig. 19: Application Page

Fig. 19: Application Page

Hope this helped :)

6. Conclusion

Through this example, we have learned about the HttpSessionListener implementation in jsf which was deployed using the Tomcat7 application server.

7. Download the Eclipse Project

This was a JSF EventQueue example with Eclipse and Tomcat

You can download the full source code of this example here: JSF EventQueue

Do you want to know how to develop your skillset to become a Java Rockstar?

Subscribe to our newsletter to start Rocking right now!

To get you started we give you our best selling eBooks for FREE!


1. JPA Mini Book

2. JVM Troubleshooting Guide

3. JUnit Tutorial for Unit Testing

4. Java Annotations Tutorial

5. Java Interview Questions

6. Spring Interview Questions

7. Android UI Design


and many more ....


Receive Java & Developer job alerts in your Area


Notify of

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Inline Feedbacks
View all comments