Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

  1. Under the project explorer right click on the SimpleJSF project and create a new class.



  2. Fill the New Java Class form with jsf as the package name and FirstName as the bean class name. Select Finish once done.




  3. Add the following code to the FirstName bean class:
    Code Block
    JAVA
    borderStylesolid
    titleFirstName.java
    borderStylesolid
    JAVA
    package jsf;
    
    public class FirstName {
    	String username;
    
    	public String getName() {
    		return username;
    	}
    
    	public void setName(String name) {
    		username = name;
    	}
    
    }
    

  4. Create a second Bean class LastName and add the following code to the class:
    Code Block
    borderStyle
    JAVAsolid
    titleLastName.java
    borderStylesolid
    JAVA
    package jsf;
    
    public class LastName {
    	String lastname;
    
    	public String getLName() 	{
    		return lastname;
    	}
    
    	public void setLName(String lname)
    	{
    		lastname = lname;
    }
    }
    
    This completes the Model definition and implementation of the bean classes.

...

  1. Right click on WebContent and create a new folder with the name pages.



  2. Right click on pages folder and create a JSP called login.jsp. Select Finish.



  3. Similarly create another JSP page called welcome.jsp.

  4. Now we have to include the Tag Library Descriptors (TLD) in our application. Geronimo comes packaged with the required TLD's, which can be found in:
    solid
    No Format
    borderStyle
    titleLocation of TLD
    borderStylesolid
    <GERONIMO_HOME>\repository\org\apache\myfaces\core\myfaces-impl\1.2.3\myfaces-impl-1.2.3.jar\META-INF\myfaces-html.tld
    and
    <GERONIMO_HOME>\repository\org\apache\myfaces\core\myfaces-impl\1.2.3\myfaces-impl-1.2.3.jar\META-INF\myfaces_core.tld
    

  5. To add these two TLD's in the application, in Eclipse under the Project Explorer right click on WEB-INF. Create a folder called tld. Copy myfaces-html.tld and myfaces_core.tld to this folder.

  6. The next step is to populate login.jsp and welcome.jsp with data
    Code Block
    ActionScriptborderStylesolid
    titlelogin.jsp
    borderStylesolid
    ActionScript
    <%@ taglib uri="/WEB-INF/tld/myfaces-html.tld" prefix="h" %>
    <%@ taglib uri="/WEB-INF/tld/myfaces_core.tld" prefix="f" %>
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
    <title>Welcome to Apache Geronimo</title>
    </head>
    <body>
    <f:view>
        <h1><h:outputText value="Welcome to Apache Geronimo" /></h1>
        <h:form>
            <h:message for="firstName" style="color: red;" />
            <h:message for="lastName" style="color: red;" />
            <br>
            <h:outputText value="Enter your first name" />
            <br>
            <h:inputText id="firstName" value="#{firstName.name}" required="true">
                <f:validateLength minimum="4" maximum="10" />
            </h:inputText>
            <br>
            <h:outputText value="Enter your last name" />
            <br>
            <h:inputText id="lastName" value="#{lastName.LName}" required="true">
                <f:validateLength minimum="3" maximum="10" />
            </h:inputText>
            <br>
            <h:commandButton id="submit" action="validated" value="Enter" />
        </h:form>
    </f:view>
    </body>
    </html>
    
    Code Block
    ActionScriptborderStylesolid
    titlewelcome.jsp
    borderStylesolid
    ActionScript
    <%@ taglib uri="/WEB-INF/tld/myfaces-html.tld" prefix="h"%>
    <%@ taglib uri="/WEB-INF/tld/myfaces_core.tld" prefix="f"%>
    <%@ page language="java" contentType="text/html; charset=ISO-8859-1"
    pageEncoding="ISO-8859-1"%>
    <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
    <html>
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
    <title>Welcome</title>
    </head>
    <body>
    <f:view>
    <h3><h:outputText value="You have successfully logged in: " /> <h:outputText value="#{firstName.name} " /> <h:outputText value="#{lastName.LName}" />
    <h:outputText value="!" /></h3>
    </f:view>
    </body>
    </html>
    
    Lets now try to understand what each line of code represents.
    • The first two lines in login.jsp defines two tag libraries
      Code Block
      ActionScript
      borderStylesolid
      titleCode Snippet from login.jsp
      borderStylesolid
      ActionScript
      <%@ taglib uri="/WEB-INF/tld/myfaces-html.tld" prefix="h" %>
      and
      <%@ taglib uri="/WEB-INF/tld/myfaces_core.tld" prefix="f" %>
      
      These two sets of tags are defined by JSF. The first one with the namespace "h" is used to generate html views. The second one with the namespace "f" handles the core functionalities of JSF like type conversions, validations and listeners for input from user.
    • The next few lines contains the usual html tags
      Code Block
      ActionScript
      borderStylesolid
      titleCode Snippet from login.jsp
      borderStylesolid
      ActionScript
      <html>
      <head>
      <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
      <title>Welcome to Apache Geronimo</title>
      </head>
      <body>
      
    • The tag <f:view> represents the start of JSF code.
    • This line of code Represents the input tag. The id="firstName" and value="firstName.name" comes from the Managed Bean.
      Code Block
      ActionScript
      borderStylesolid
      titleCode Snippet from login.jsp
      borderStylesolid
      ActionScript
      <h:inputText id="firstName" value="#{firstName.name}" required="true">
      
  7. Using the Faces Configuration Editor, select firstName bean under Managed Bean tab. The Managed Bean Name is firstName. See the figure below.



    This completes the implementation of View (V) in the application. The other tags <f:validateLength> and <h:commandButton> will be explained in the next section.

...

  1. Launch the Faces Configuration Editor by double clicking on faces-config.xml

  2. Select the Navigation Rule tab in the Configuration Editor. Under the Palette window select Page. This will select a PageFlow Page GUI object.



  3. Drag the mouse over the Navigation Rule Window and click on the window. This will give a Select JSP File window. Select the login.jsp as shown in the figure and select OK.




  4. Similarly add the welcome.jsp page on the Navigation Rule window. See the figure below:




  5. Select Link from the Palette window and join the two pages as shown in the figure:




  6. Select the link between the two pages and go to properties view and set the value for From Outcome field as validated. This is because of the tag <h:commandButton id="submit" action="validated" value="Enter" />. Once all the inputs are valid the action taken is validated. See the figure.



  7. Once done have a look the Source tab in the Faces Navigation Editor. A <navigation-rule> tag has been introduced into the faces-config.xml. This rule instructs the Controller that if all the inputs are valid from a form in the /pages/login.jsp, and the action is validated, then go to page /pages/welcome.jsp.




  8. Now lets add a index.jsp under WebContent as follows:
    Code Block
    ActionScript
    borderStylesolid
    titleindex.jsp
    borderStylesolid
    ActionScript
    <%@ page language="java" contentType="text/html; charset=ISO-8859-1"pageEncoding="ISO-8859-1"%>
    <\!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
    <html>
    <body>
    <jsp:forward page="/pages/login.jsf" />
    </body>
    </html>
    
    What is the login.jsf in the forward path tag. If you look at the web.xml, *.jsf is used as the URL pattern to suggest that forwarded page be taken care by Java Server Faces Servlet.
    This completes the Application Development process. The next step is to deploy and test the application.

...