Skip to main content

The HelloWorld example of JSF 2.2 with Myfaces

I just did by myself create a very simple app "HelloWorld" of JSF 2.2 with a concrete implementation Myfaces that we can use it later on for our further JSF trying out. I attached the source code link at the end part. Just follow these steps below:

1. Create a Maven project in Eclipse (Kepler) with a simple Java web application archetype "maven-archetype-webapp". Maven should be the best choice for managing the dependencies, so far. JSF is a web framework that is the reason why I chose the mentioned archetype for my example.

2. Import dependencies for JSF implementation - Myfaces (v2.2.10) into file pom.xml. The following code that is easy to find from http://mvnrepository.com/ with key words "myfaces".

<dependency>
 <groupId>org.apache.myfaces.core</groupId>
 <artifactId>myfaces-api</artifactId>
 <version>2.2.10</version>
 </dependency>
<dependency>
 <groupId>org.apache.myfaces.core</groupId>
 <artifactId>myfaces-impl</artifactId>
 <version>2.2.10</version>
</dependency>

3. As any other web frameworks, we need to configure for JSF stuffs in file web.xml, follow this http://myfaces.apache.org/wiki/core/user-guide/getting-started/configuring-myfaces.html

<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  
 xmlns="http://java.sun.com/xml/ns/javaee" 
 xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" 
 xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd" 
 version="2.5">
 
 <!-- JSF mapping -->
 <servlet>
  <servlet-name>Faces Servlet</servlet-name>
  <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
  <load-on-startup>1</load-on-startup>
 </servlet>
 <servlet-mapping>
  <servlet-name>Faces Servlet</servlet-name>
  <url-pattern>*.xhtml</url-pattern>
 </servlet-mapping>
  
  <!-- welcome page -->
  <welcome-file-list>
    <welcome-file>index.xhtml</welcome-file>
  </welcome-file-list>
</web-app>

4. Create a Managed Bean by Java classes and  use JSF tags in index.xhtml for testing

Java code:

package vn.nvanhuong.jsf_myfaces;

import javax.faces.bean.ManagedBean;

@ManagedBean(name = "helloBean")
public class HelloManagedBean {
 
 public HelloManagedBean() {
  this.greeting = "Hello JSF - Myfaces";
 }

 private String greeting;

 public String getGreeting() {
  return greeting;
 }

 public void setGreeting(String greeting) {
  this.greeting = greeting;
 }
}

XHTML code:

<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml"
 xmlns:f="http://java.sun.com/jsf/core"
 xmlns:h="http://java.sun.com/jsf/html">
 <h:head>
  <title>JSF - Myfaces Example</title>
 </h:head>
 <h:body>
  <h:outputText value="#{helloBean.greeting}"/>
 </h:body>
</html>

5. Run the application on server Tomcat (v7.0)

http://localhost:8080/jsf_myfaces/



Source code: https://github.com/vnnvanhuong/jsf_myfaces



References:

[1]. http://myfaces.apache.org/wiki/core/user-guide/getting-started/configuring-myfaces.html

[2]. http://mvnrepository.com/

[3]. http://docs.oracle.com/javaee/6/tutorial/doc/bnaxj.html

















Labels





















Labels:
































Comments











Post a Comment



















Popular posts from this blog





















[Snippet] CSS - Child element overlap parent




























I searched from somewhere and found that a lot of people says a basic concept for implementing this feature looks like below:  HTML code:  <div id="parent">  <div id="child">   </div> </div>  And, CSS:  #parent{   position: relative;   overflow:hidden; }  #child{   position: absolute;   top: -1;   right: -1px; }   However, I had a lot of grand-parents in my case and the above code didn't work. Therefore, I needed an alternative. I presumed that my app uses Boostrap and AngularJs, maybe some CSS from them affects mine. I didn't know exactly the problem, but I believed when all CSS is loaded into my browser, I could completely handle it.      www.tom-collinson.com    I tried to create an example to investigated this problem by Fiddle . Accidentally, I just changed: position: parent;  to position: static;  for one of parents -> the problem is solved.  Look at my code:   <div class="modal-body dn-placeholder-parent-positi...




















Post a Comment









Read more




























A User Guide To Working With Huong




























  Introduction I write this user guide to help us (you and me) have a good collaboration at work. I hope you also share yours. How I view success We all feel passionate and happy at work. We all enjoy discussing transparently. We take it easy to give and receive feedback. After all, we together develop and bring valuable applications to users. How I communicate I mostly prefer a face-to-face conversation. Just leave me a message on Slack if you don't want to come to my desk. For a big topic which takes more than 30 minutes, we should have a meeting. Only send me emails only if stuff is very formal or out-of-office hours Things I do that may annoy you I do practice the Pomodoro technique so that sometimes you see me in the "do not disturb" mode. Often to make things clear, I am at ease talking   frankly   with you. What gains and loses my trust It is easy to gain my trust when you commit to what you say. You show your passion and endeavors to achieve that. It is easy to lo...




















Post a Comment









Read more




























Java 8 - Persistent data structure




























  The following is a series of posts about "functional programming in Java" which is the result of my understanding by reading the book " Java 8 in Action: Lambdas, Streams, and Functional-style Programming, by Alan Mycroft and Mario Fusco ".  1. Why functional programming?  2. Functional programming in Java 8  3. Java 8 - Using Functions as Values  4. Java 8 - Persistent data structure   Persistent data structure is also known as a simple technique but it's very important. Its other names are functional data structure and immutable data structure.   Why is it "persistent"?  Their values persist and are isolated from changes happening elsewhere. That's it!  This technique is described as below:   If you need a data structure to represent the result of a computation, you should make a new one and not mutable an existing data structure.   Destructive updates  version  public static A doSomething(A a){     a.setProp1("new value");     return...




















1 comment









Read more




























[Snippet] Generate a new unique "name" string from an existing list




























Suppose that we have a list of employees. Everytime, we want to add new employee into this list, the name of the employee will be generated with the following rules:  - the name of the new one is set to " [originalname] 1 " - in case the name already exist, " [originalname] 2 " is used, and so on.   Here is my code snippet by Javascript:  var employees =[     {id: 1, name: 'name'},     {id: 2, name: 'name 1'},     {id: 3, name: 'name 2'},     {id: 5, name: 'name 4'} ];  var commonUtils = {    isExistName: function(_name, _collection, _prop) {        for(var i = 0; i< _collection.length; i++){        if(_collection[i][_prop].localeCompare(_name)==0){          return true;       }      }        return false;   },      generateNewName: function(_name, _collection, _prop){     var i = 1;     var searching = true;     while (searching) {       var newName = _name+ " " + i;       if (!this.isExistName(newName, _collection, _pro...




















Post a Comment









Read more






























The power of acceptance test




























 User Story is the place PO gives his ideas about features so that developers are able to know what requirements are. Acceptance tests are these show the most valuable things of the features represented by some specific cases. Usually PO defines them, but not always. Therefore, refining existing acceptance tests – even defining new ones that cover all features of the User Story must be a worth task.     Acceptance test with Given When Then  pattern    If we understand what we are going to do, we can complete it by 50%  I have worked with some members those just start implementing the features one by one and from top to down  of the User Story description. Be honest, I am the one used to be. What a risky approach! Because it might meet a case that is very easy to miss requirements or needs to re-work after finding any misunderstood things.   I have also worked with some members those accept spending a long time to clarify the User Story. Reading carefully of whole User Story by defining...




















Post a Comment









Read more