Category Archives: JSF

XPages: Make your PhaseListener Thread Safe

When implementing a JavaServer Faces (JSF) based framework for your XPages, you may decide to use a PhaseListener, or two, or three, or any number you want. PhaseListeners can be very powerful tools to help perform centralized processing for your application. Before we dive into the main topic of this article, it may be helpful to provide a base understanding of PhaseListeners and how to define one. If you already know how to use a PhaseListener then feel free to jump the next section.

What is a PhaseListener and how would I use it?

As JSF processes requests it fires specific events. These events are called Continue reading

Share:

Using JSF Framework Development Standards for your XPages Project (Part Five: The View)

In the previous installment of this series we completed our Model layer described in the Model-View-Controller (MVC) architecture. In that article we covered the façade (or service) layer:

  • EmployeeCRUDFacade: A service layer class to handle data manipulation and data business rules for access by client code that should not work directly with the model layer.

Examples of data manipulation code and data business rule code include:

  • Calculate the age of an employee. Your database holds a birthdate, but not an age.
  • Calculate the number of years an employee has worked for your company. Your database holds a hire date but not a length of time.
  • Calculate the number of approvals required for a time off request that exceeds a certain number of hours.

Examples of client code that should never access the model directly include:

  • Workflow processing code.
  • External system integration code.
  • UI code (a managed bean…covered in this article).

It may appear on the initial design of an application that this layer is just adding extra code. In other words, why not just let my view bean access the DAO? Continue reading

Share:

Using beans as validators in XPages

This article describes how you can create your custom validators by implementing javax.faces.validator.Validator interface. But one problem with this is that you need to create a separate Java class for each validation, for e.g. you would have individual Java classes for validating email, credit card number and so on. And for each Java class you have to add <validator>…</validator> entry in faces-config.xml.

Continue reading

Share:

Editing faces-config.xml with content assist in Domino Designer

Many a times while editing faces-config.xml I felt the need of content assist which could provide me with available tags and its attributes to ease development. JSF provides a DTD for faces-config.xml which can be used for this purpose.

Include this DOCTYPE in your faces-config.xml file

< !DOCTYPE faces-config PUBLIC
"-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.0//EN"
"http://java.sun.com/dtd/web-facesconfig_1_0.dtd">

Continue reading

Share: