Creating JavaServer Faces Maven Managed Projects with Eclipse

NOTE: See the blog post How I Created a Standard pom.xml file for Eclipse and NetBeans for the final version of the pom.xml

Step 1

Create a project based on my blog “UPDATED Setting up a JEE 6 Web Profile Maven Project in Eclipse using TomEE”.

Step 2

Eclipse reveals its special capabilities such as specialized editors based on the project’s facet. As it now stands the project you just created will allow you to create Servlet/JSP applications. You need to add the JavaServer Faces facet to the project.

Right mouse click on the project and select Properties and then select Project Facets. You will see:


You now need to add the JavaServer Faces facet version 2.1, change the Java version to 1.7 and uncheck JAX-RS. It should now look like:


The version of TomEE, 1.6.0, that I am using does not yet have JSF 2.2 in its library. Its current version is 2.1. If you need to use 2.2 then there is a beta version of the library available as of this writing.

Do not click on OK yet.

Step 3

Notice the link just above the buttons that reads “Further configuration required…”. Click on it and you will see:


Pull down the combo box at the top labeled “Type:” and select Disable Library Configuration to replace User Library. This is necessary because the JSF libraries are already in the lib folder of TomEE and Maven knows what libraries are required.

It should now look like:


While it is possible to create a JSF application without the JSF servlet deployment descriptor the Eclipse tools use it in some instances. The checkbox must be checked and the values that show in the textboxes can be left as they appear.

Click OK and then OK again.

Step 4

Save all your files. Right mouse click on the project and select Maven -> Update Project. When this is complete you will have errors such as:


The solution was found by entering the first of the Maven Java EE Configuration Problems into Google. “Type Cannot change version of project facet Dynamic Web Module to 2.5.” led me to a Stack Overflow question that pointed out that the <web-app> attributes in the web.xml file needed to be changed. The generated web.xml read:

<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="" 
     <servlet-name>Faces Servlet</servlet-name>
     <servlet-name>Faces Servlet</servlet-name>

The <web-app> needed to read:

<web-app xmlns:xsi=

Simply put, you need to replace the 2_5 with 3_0 and the 2.5 with 3_0.

Save files and do another Maven->Update Project and the errors all disappear.

Step 5

The errors are gone but a mysterious entry in Markers appears:


Searching for this revealed two solutions. One was to go into Windows -> Preferences -> Java -> Debug and un-select “Suspend execution on uncaught exceptions”. I did this and it made no difference.

The second solution was to right mouse click on the two Unknown descriptions, right mouse click and delete. You are warned that they may come back but in my case after a Maven -> Update Project and a Run -> Maven Build the markers did not return.

You are now ready to create a JavaServer Faces application. Projects created this way will open and execute successfully in NetBeans when the project is saved to a Subversion repository.


Email this to someoneTweet about this on TwitterShare on LinkedIn0Share on Facebook0

One thought on “Creating JavaServer Faces Maven Managed Projects with Eclipse

  1. Tati

    I had the similiar exeirpence when I ported a j2me app from another phone to 3650 (t-mobile not attws). Try to do this:Before you send a request, set the User-Agent, Content-Length etc. like this: conn = (HttpConnection); conn.setRequestProperty( User-Agent , Profile/MIDP-1.0 Configuration/CLDC-1.0 ); conn.setRequestProperty( Content-Language , en-US ); conn.setRequestProperty( Connection , close ); conn.setRequestMethod(HttpConnection.POST); conn.setRequestProperty( Content-Length , Integer.toString( msgByte.length ) ); os = conn.openOutputStream(); If this can not fix your problem, install the HttpTest to your phone (it comes with Java Wireless Toolkit). If it works, read the http codes.

Leave a Reply

Your email address will not be published. Required fields are marked *