Hadole, Nishant IN BOM SISL wrote:
Dear Simone,

The obvious error displayed from log is " java.lang.NoClassDefFoundError: 
org/apache/xerces/util/EncodingMap". First check whether the xerces jar containing 
mentioned class is in place. Try downloading new jar and again restart the tomcat 
services.


I am no great Java or Eclipse expert, but sometimes one wonders how explicit an error log message must be, that one would notice.

In the submitted logfile, these two errors happen first :

> 16-feb-2010 16.48.14 org.apache.catalina.loader.WebappClassLoader validateJarFile > INFO: validateJarFile(C:\Program Files\Apache\Tomcat55\webapps\Calzedonia2007\WEB-INF\lib\j2ee.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class > 16-feb-2010 16.48.14 org.apache.catalina.loader.WebappClassLoader validateJarFile > INFO: validateJarFile(C:\Program Files\Apache\Tomcat55\webapps\Calzedonia2007\WEB-INF\lib\javaee.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class

In section 9.7.2 of the servlet spec, it says :

SRV.9.7.2 Web Application Class Loader

...
As described in the J2EE license agreement, servlet containers that are not part of a J2EE product should not allow the application to override J2SE platform classes, such as those in the java.* and javax.* namespaces, that J2SE does not allow to be modified. Also, servlet containers that are part of a J2EE product should not allow the application to override J2SE or J2EE platform classes, such as those in java.* and javax.* namespaces, that either J2SE or J2EE do not allow to be modified. The container should not allow applications to override or access the container’s implementation...

I would tend to interpret this as :
- this web application tries to load jar files containing classes which would redefine classes of the JVM. The log message also indicates which jar's that is. - the container (Tomcat) thus - rightly according to the spec - rejects the loading of these jar's. - and then, later on, something else fails, maybe because another class (which may also have been in these rejected jar's) is missing.

Should not the first two errors above be attended to first ?




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to