7 Feb
2010
7 Feb
'10
12:11 p.m.
Gotcha. gwt-servlet-1.5.3 was hanging around in tomcat/lib.
Removing it and restarting it solved it.
It's not the first time I have such a mismatch, I wonder if it would
not be good to write a little sanity test for it and warn the user in
case.
Also, the fact that my error created a "zero action", not an error
panel, is somewhat bad for me. I would prefer the user to be "sent an
error panel in the face" instead of the tab click be as if it was
broken.
thanks Marius and Vincent.
paul
On 07-févr.-10, at 11:25, Marius Dumitru Florea wrote:
odd. Why would
the GWT servlet act differently in jetty or tomcat? I
would understand it with static files but not the GWTservlet.
Odd indeed. Can you try to remove gwt-servlet-2.0.0.jar from the
WEB-INF/lib directory and see if you can (re)start the server this
way?
(I get java.lang.NoClassDefFoundError:
com/google/gwt/user/client/rpc/RemoteService) Maybe a different
version
of gwt-servlet is loaded by Tomcat.