Executing Method on pageload

Question

Hello,
I'm looking for a solution to execute a method on a backing bean, when a view is loaded. Well I could workaround that with using a commandButton to link to the page and execute the method as an action handler, but that's not really an elegant solution.
Good ideas highly appreciated!
Best regards,
Timo Elverkemper

Answer 1

hallo little
hope u find the answer from the below desc.
phaselistener is called for every page load...
JSF PhaseListener - Is This User Logged In?
JavaServer Faces (JSF) is being touted as the next generation of web application development from the powers that be (IBM, Sun, Oracle), and has been tugging at my interest the past 8 months. In my quest to use it I quickly found myself drowning in the different complexities, but through much head to wall banging I have prevailed and would like to share some of those experiences with you through tips.
This tip shows how to register a PhaseListner at the Restore View phase of the JSF Lifecycle. The PhaseListener checks to see if the user has logged in, and if not it returns them to the login page. One could check to see if a user is logged in on each page and have code duplicated across many different backing beans, but going the PhaseListener route guards against that and allows you to have one point of checking for login credentials. To learn more about the JSF Lifecycle point your browser to http://www.javaworld.com/javaworld/jw-11-2002/jw-1129-jsf-p2.html
Figure 1 shows how to register the PhaseListener using the lifecycle and phase-listener tags. This should be placed in your faces configuration file, often named faces-config.xml.
Figure 1
<lifecycle>
<phase-listener>com.loffler.copycenter.controller.LoggedInCheck</phase-listener>
</lifecycle>
Figure 2 shows Java class LoggedInCheck implementing PhaseListener. The method getPhaseId is used to tell the PhaseListner which lifecycle phase this class should be called. In this example PhaseId.RESTORE_VIEW is used. You will have to understand the different phases to make sure a particular one fits for you. This one works in this case because it happens after backing beans have been updated form data from the web page.
Figure 2
package com.mowyourlawn.controller;
import javax.faces.application.NavigationHandler;
import javax.faces.context.FacesContext;
import javax.faces.event.PhaseEvent;
import javax.faces.event.PhaseId;
import javax.faces.event.PhaseListener;
public class LoggedInCheck implements PhaseListener {
    public PhaseId getPhaseId() {
        return PhaseId.RESTORE_VIEW;
    public void beforePhase(PhaseEvent event) {
    public void afterPhase(PhaseEvent event) {
        FacesContext fc = event.getFacesContext();
        // Check to see if they are on the login page.
        boolean loginPage =
          fc.getViewRoot().getViewId().lastIndexOf("login") > -1 ? true : false;
        if (!loginPage && !loggedIn()) {
            NavigationHandler nh = fc.getApplication().getNavigationHandler();
            nh.handleNavigation(fc, null, "logout");
    private boolean loggedIn() {
        return LoginController.loggedIn().booleanValue()c;
Figure 3 shows what happens when a from-outcome of �logout� is encountered. Reference the nh.handleNavigation(fc, null, "logout"); line of code in Figure 2 to understand how the two are related. Again this should be placed in your faces-config.xml file.
Figure 3
<navigation-rule>
  <from-view-id>*</from-view-id>
    <navigation-case>
      <from-outcome>logout</from-outcome>
      <to-view-id>/login.jsp</to-view-id>
    </navigation-case>
</navigation-rule>
The above article was written by Aaron Bartell. If you have any questions
about this article, contact Aaron at mailto:[email protected].