Problem Solver

Easy Page Actions with Facelets

By , 28 August 2007

Easy Page Actions with Facelets

It appears that everybody has come up with their own way to implement page actions in JSF. i.e. execute some code before a page is processed/rendered, like you did in Struts. Well, it turns out that I occasionally need this too (surprisingly infrequently though), so I had a look at how Shale and Seam solve the problem.

Shale uses faces-config.xml to map view ids to managed beans which implement a ViewController interface [1]. Okay, that seems alright, but it means more xml and more classes. Often I just need to put a request-scope attribute in place, so this feels like too much work to me. Seam allows you to map view ids to method expressions via a pages.xml configuration file [2]. This means no extra beans, but does mean more configuration. Can it be done with no xml and no new beans?

Yes! And the tool for the job has probably been in your toolkit all along - Facelets TagHandlers.

Easy Page Actions with Facelets

There are two advantages to using TagHandlers to implement page actions:

  1. They are only executed once during the tree build, so don't interfere with the rest of the lifecycle or cause EL to be evaluated multiple times (like some components).
  2. There is no need to map the view id since the TagHandler is placed directly in the template for the view.

The Java code for the TagHandler is very simple:

 * This tag evaluates a method expression, so it can be used to implement
 * 'page actions' since it is only executed when the view is built.
public class ActionHandler extends TagHandler {
    private final TagAttribute method;
    public ActionHandler(TagConfig config) {
        this.method = this.getRequiredAttribute("method");

    /** evaluate the method expression */
    public void apply(FaceletContext ctx, UIComponent parent) {
        method.getMethodExpression(ctx, null, new Class[] {}).
                invoke(ctx.getFacesContext().getELContext(), null);

To use the action, you must map it in your facelets taglib:


and then put it into the template where it is needed, e.g.:

<ui:composition xmlns=""
  <!-- merge the user into the current persistence context -->
  <fc:action method="${modules.forums.mergeUser}"/>
  <!-- then show their profile -->
  <h:outputText value="${}"/>

You should note though, that the TagHandlers aren't invoked on a postback, so if this is a part of your requirements you could use a PhaseListener, or the Seam or Shale approach.

This code will be available in the next version of the Furnace Webapp Framework.




About Roger Keays

Easy Page Actions with Facelets

I am an artist, an engineer, and a student of psychology. Some projects I'm working on at the moment are Sunburnt SEO, The Game Of Your Life, Money Talks and other, top secret stuff. You can follow me via RSS or on Twitter, Facebook, and even Google+.

Add a comment

Please visit to add your comments.

Comment posted by: Shane Genschaw, 6 years ago

Tim, change it "invoke(ctx, null);" instead.  (FaceletsContext extends ELContext).


Comment posted by: Tim Büthe, 7 years ago


can I somehow make this work with JSF 1.1? The method getELContext is new in 1.2, so I get an error in this line:

invoke(ctx.getFacesContext().getELContext(), null);



Comment posted by: cp, 7 years ago

cool. tnx 

Comment posted by: , 7 years ago

The method you bind to can just have no parameters and a void return type, e.g:

public void mergeUser() {
   user = em.merge(user);

Follow Roger Keays

It'll Change Your Life

I write every Sunday about all sorts of interesting stuff. Drop me your email and you'll be the first to get my articles when they're published. It'll change your life. And it's free :)

Website Updates

Latest Poll

Is your life is better or worse because of Facebook?
The same