CODEWITHSUNDEEP
javatomcatjsfnetbeans
Yurish
Yurish

Reputation: 1309

Problems with deploying JSF project from Netbeans to Tomcat

Googled everything, but can't find solution for my problem.

When i'm trying to deploy my project to Tomcat, i have such errors in Tomcat log:

    SEVERE: Error configuring application listener of class com.sun.faces.config.ConfigureListener
    java.lang.NoClassDefFoundError: javax/servlet/ServletRequestListener

I tried to deploy it from fresh Netbeans 6.8 to fresh Tomcat 6.0.26, but the problem is still there.

Servlet-api.jar is in the tomcat/lib folder. Tried to replace it with the newest, but problem is still there.

No compilation errors. Everything is correct.

Problem started suddenly. No code changes, no new jars added.

Help?

UPD: contents of WEB-INF/lib:

Upvotes: 1

Views: 4725

Answers (2)

Jarek Rozanski
Jarek Rozanski

Reputation: 800

Tomcat doesn't ship with JSF libraries, so you have to include those in WEB-INF/lib. From the listing above it is obvious that your are missing those. For JSF2 go here.

Moreover you do not need servlet-api in WEB-INF/lib, it is a provided library.

Upvotes: 0

BalusC
BalusC

Reputation: 1108557

java.lang.NoClassDefFoundError: javax/servlet/ServletRequestListener

The javax.servlet.ServletRequestListener is newly introduced since Servlet 2.4 API. That your environment cannot seem to find it can be caused by two things:

  1. Either the web.xml is declared as Servlet 2.3 or older which forces the server to Servlet 2.3 compliance mode, or the server in question doesn't support Servlet 2.4 at all.

  2. Classpath is really, really messed up. You should never put/change/remove libraries in JRE/lib, JRE/lib/ext or Tomcat/lib without understanding what you're doing. You should never put appserver-specific libraries in Webapp/WEB-INF/lib because that doesn't make any sense.

To fix 1, ensure that your web.xml is declared as at least Servlet 2.4. Preferably the newest which the server can support. Tomcat 6.0 supports Servlet 2.5, so declare web.xml accordingly.

To fix 2, cleanup the classpath of all pollution. Invest some more time to learn more about the phenomeon "classpath". Handle it with care.

Upvotes: 3

Related Questions