Thank you very much Henry,
I upgraded and digested to a minimum web.xml but the problem persists. Here is it now, with same schema
used by other applications:
<web-app xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
version="2.5">
<display-name>ps-hzplan</display-name>
<servlet>
<servlet-name>hzplan</servlet-name>
<servlet-class>com.vaadin.terminal.gwt.server.ApplicationServlet</servlet-class>
<init-param>
<description>Vaadin application class to start</description>
<param-name>application</param-name>
<param-value>net.cbsolution.ps.hzplan.Main</param-value>
</init-param>
<init-param>
<description>Application widgetset</description>
<param-name>widgetset</param-name>
<param-value>net.cbsolution.ps.hzplan.widgetset.Ps_hzplanWidgetset</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>hzplan</servlet-name>
<url-pattern>/ps-hzplan/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>hzplan</servlet-name>
<url-pattern>/VAADIN/*</url-pattern>
</servlet-mapping>
</web-app>
I have also added a second servlet mapping for widgetset after a similar problem I found in another post,
but in that case there was a clear “class not found” error, but I added it, just in case…
I am not packaging the war each time but directly editing the file in /tomcat/webapps/ directory and restarting tomcat (that should be the same).
I also tried to remove context.xml file (from META-INF) thai I used an a (failed) attempt to avoid serialization
errors constantly issued by Tomcat at startup (from another Vaadin post):
<!-- Turn off session serialization -->
<Manager className="org.apache.catalina.session.PersistentManager"
debug="0" distributable="false" saveOnRestart="false">
<Store className="org.apache.catalina.session.FileStore"/>
</Manager>
I also removed it from tomcat/conf. Same result: no stack trace.
If there would be a stack trace I would at least have a starting point to locate the problem, like some class
missing.
What I really do not understand (it is not a Vaadin problem) how Tomcat can produce a severe error and not stack trace. Should I possibly report the error to tomcat mailing list?
Another alternative would be to deploy on another container, like jetty or glassfish, but since all project was developed under Tomcat I wouldn’t like to change many things at the same time.
Thank you anyway very much for your so quick reply!
