Skip to main content

Making a simple JSF application

Here's how we build a simple JSF application:

  1. Configure web.xml for FacesServlvet
  2. Create faces-context.xml (This is the file from where FacesServlet reads navigation rules, details of managed beans and other JSF specific configuration details)
  3. Create a controller or controllers for the application. Here is where JSF differs from Struts. Struts had a front controller, the ActioServlet which delegated requests to Action classes. JSF does not have the notion of a front controller. A JSF application uses an event model. The UI is tied to the backend with events. Controller classes (also known as backing beans in JSF) accept these events and also hold properties that accept user supplied values from a form. These properties will also be used to display data on pages. For example if we have a simple application that allows employees to put in a leave request, a backing bean will have properties that will be populated with the request that the user enters on the form. The same backing bean may also be responsible for displaying the leave status to the user. Essentially we will have one backing bean class for a related set of UI views. The view pages for adding, editing, viewing, and deleting "leave requests" will be mnaged by the same backing bean class. A JSF application can have many backing beans, thus resulting in many controllers. Even though we can code business logic in these backing beans, we should desist from doing so. The business logic must in other application classes which are invoked from the backing bean. This way the backing bean acts as a glue between the view and the model (which is what a controller should be doing anyways).
  4. Create the view (JSP) files.
    1. All the JSF tags should be put within an f:view tag. Components placed within this tag are managed by the JSF system. If we not use f:view, then the JSF system will remain oblivious of the components.
    2. Fields in a JSF form can be associated with beacking bean properties using JSF - EL. For example #{BeanName.PropertyName}. JSF-EL is similar to JSTL-EL, however, it directly associates a field (within which it is used) with a backing bean property (or a properties property). These properties are used to hold values submitted by users as well as hold values that will be displayed to the user on a form.
    3. We can associate commandButtons to methods in the backing beans, using JSF-EL. I believe we can associate them with events, in which case appropriate event handlers will be invoked[verify this].
    4. The JSF system can also run simple validations on the form fields automatically. Things like required fields, or fields that represent numbers can be validated automatically. More complex validations can be defined in custom validators.


Popular posts from this blog

My HSQLDB schema inspection story

This is a simple story of my need to inspect the schema of an HSQLDB database for a participar FOREIGN KEY, and the interesting things I had to do to actually inspect it. I am using an HSQLDB 1.8 database in one of my web applications. The application has been developed using the Play framework , which by default uses JPA and Hibernate . A few days back, I wanted to inspect the schema which Hibernate had created for one of my model objects. I started the HSQLDB database on my local machine, and then started the database manager with the following command java -cp ./hsqldb- org.hsqldb.util.DatabaseManagerSwing When I tried the view the schema of my table, it showed me the columns and column types on that table, but it did not show me columns were FOREIGN KEYs. Image 1: Table schema as shown by HSQLDB's database manager I decided to search on StackOverflow and find out how I could view the full schema of the table in question. I got a few hints, and they all pointed to

Fuctional Programming Principles in Scala - Getting Started

Sometime back I registered for the Functional Programming Principles in Scala , on Coursera. I have been meaning to learn Scala from a while, but have been putting it on the back burner because of other commitments. But  when I saw this course being offered by Martin Odersky, on Coursera , I just had to enroll in it. This course is a 7 week course. I will blog my learning experience and notes here for the next seven weeks (well actually six, since the course started on Sept 18th). The first step was to install the required tools: JDK - Since this is my work machine, I already have a couple of JDK's installed SBT - SBT is the Scala Build Tool. Even though I have not looked into it in detail, it seems like a replacement for Maven. I am sure we will use it for several things, however upto now I only know about two uses for it - to submit assignments (which must be a feature added by the course team), and to start the Scala console. Installed sbt from here , and added the path

Five Reasons Why Your Product Needs an Awesome User Guide

Photo Credit: Peter Merholz ( Creative Commons 2.0 SA License ) A user guide is essentially a book-length document containing instructions for installing, using or troubleshooting a hardware or software product. A user guide can be very brief - for example, only 10 or 20 pages or it can be a full-length book of 200 pages or more. -- As engineers, we give a lot of importance to product design, architecture, code quality, and UX. However, when it comes to the user manual, we often only manage to pay lip service. This is not good. A usable manual is as important as usable software because it is the first line of help for the user and the first line of customer service for the organization. Any organization that prides itself on great customer service must have an awesome user manual for the product. In the spirit of listicles - here are at least five reasons why you should have an awesome user manual! Enhance User Satisfaction In my fourteen years as a