I used vaadin to make an applcation and on my computer, all works fine …
But i want to upload the application in professionnal host i paid …
The host is running with Tomcat 5.5 and JAVA 6 …
I have this error :
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Failed to load application class: com.proresil.views.ProresilApplication
com.vaadin.terminal.gwt.server.ApplicationServlet.init(ApplicationServlet.java:71)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200)
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773)
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703)
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:895)
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
java.lang.Thread.run(Thread.java:619)
note The full stack trace of the root cause is available in the Apache Tomcat/5.5.27 logs.
I upload the content of “WebContent” directory on the server, i upload all class files too …
After new try, i haven’t any errors in TOMCAT logs (catalina.out) …
The application works fine in my computer (eclipse + tomcat) but when i upload my application in my host (rent in professionnal) i have an error when i tried to access …
Your application is not finding the default widgetset (a.k.a the client-side GWT components). Quite often this happens when running the application as root (/) locally, and then under a specified path on the server (e.g /myapp/). If this is indeed the case, you have two options:
a) Let tomcat serve the resources statically: Extract the widgetsets and themes from the JAR - they are in a directory called VAADIN, which should be placed right next to WEB-INF (i.e /some/path/WEB-INF and /some/path/VAADIN).
b) Have Vaadin serve the resources dynamically: This requires you to register ApplicationServlet to /VAADIN/* - just add another servlet-mapping for your application with the uri-pattern /VAADIN/*
Vaadin application servlet version: 6.0.1
Widget set is built on version: 6.0.1
Application version: NONVERSIONED
inserting load indicator
Making UIDL Request with params: init
Server visit took 276ms
Communication error: com.google.gwt.core.client.JavaScriptException: (SyntaxError): missing ) in parenthetical fileName: http://proresil.ch/Test/VAADIN/widgetsets/com.vaadin.terminal.gwt.DefaultWidgetSet/735127F5A96DFC6E554FCC69B8211878.cache.html lineNumber: 454 stack: Csb()@:0 eval("( HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n\n\n\n
Not Found
\n
The requested URL /Test/UIDL/ was not found on this server.
\n
Additionally, a 404 Not Found\nerror was encountered while trying to use an ErrorDocument to handle the request.
\n\n
Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5 DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_jk/1.2.25 mod_perl/2.0.4 Perl/v5.8.8 Server at proresil.ch Port 80
\n)")@:0 Csb(" HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n\n\n\n
Not Found
\n
The requested URL /Test/UIDL/ was not found on this server.
\n
Additionally, a 404 Not Found\nerror was encountered while trying to use an ErrorDocument to handle the request.
\n\n
Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5 DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_jk/1.2.25 mod_perl/2.0.4 Perl/v5.8.8 Server at proresil.ch Port 80
\n")@http://proresil.ch/Test/VAADIN/widgetsets/com.vaadin.terminal.gwt.DefaultWidgetSet/735127F5A96DFC6E554FCC69B8211878.cache.html:454 unc([object Object]
,[object Object]
)@http://proresil.ch/Test/VAADIN/widgetsets/com.vaadin.terminal.gwt.DefaultWidgetSet/735127F5A96DFC6E554FCC69B8211878.cache.html:1432 amc([object Object]
,[object Object]
)@http://proresil.ch/Test/VAADIN/widgetsets/com.vaadin.terminal.gwt.DefaultWidgetSet/735127F5A96DFC6E554FCC69B8211878.cache.html:1469 cmc([object Object]
,[object Object]
)@http://proresil.ch/Test/VAADIN/widgetsets/com.vaadin.terminal.gwt.DefaultWidgetSet/735127F5A96DFC6E554FCC69B8211878.cache.html:1471 anb([object Object]
,[object Object]
)@http://proresil.ch/Test/VAADIN/widgetsets/com.vaadin.terminal.gwt.DefaultWidgetSet/735127F5A96DFC6E554FCC69B8211878.cache.html:235 dnb([object Object]
)@http://proresil.ch/Test/VAADIN/widgetsets/com.vaadin.terminal.gwt.DefaultWidgetSet/735127F5A96DFC6E554FCC69B8211878.cache.html:237 ([object Event]
)@http://proresil.ch/Test/VAADIN/widgetsets/com.vaadin.terminal.gwt.DefaultWidgetSet/735127F5A96DFC6E554FCC69B8211878.cache.html:277 - Original JSON-text:
HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
Not Found
The requested URL /Test/UIDL/ was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5 DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_jk/1.2.25 mod_perl/2.0.4 Perl/v5.8.8 Server at proresil.ch Port 80
http://proresil.ch/Test/UIDL must be mapped to your servlet, otherwise it won’t work. Opening the
http://proresil.ch/Test/UIDL URL in your browser should NOT give “404 Not Found”. Mapping /* to your servlet in your web.xml should be enough for both /VAADIN and /UIDL so I’m not sure where the problem is. If it works on a local Tomcat and not in your providers’ Tomcat, the providers’ Tomcat must be somehow configured differently. Of course you can also try to add a /UIDL mapping to your web.xml but I really do not see why it would help.
Vaadin is run as a normal servlet (ApplicationServlet) and it requires you to either map /* to it or both /VAADIN/* and /yourapplication/* to it. As you already did that and have it properly running on local host, the problem is most likely in your the tomcat configuration of your service provider. Without seeing that configuration it is really hard to tell. Can you deploy some other servlets?
But sorry where must i upload the war, in the server i don’t know how i must do … i tried in the root folder, where i put my webapps, but nothing appends …
In tomcat you can put the war files into /tomcat/webapps/ and it will deploy it self there when the server is running. If successful, you can see a folder under webapps with the same name as your war.
But its not running correctly and occures this error
javax.servlet.ServletException: Failed to load application class: com.example.documentmanager.DocumentmanagerApplication
at com.vaadin.terminal.gwt.server.ApplicationServlet.init(ApplicationServlet.java:71)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:857)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:135)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:928)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:539)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:298)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)