On 07-févr.-10, at 08:50, Marius Dumitru Florea wrote:
I just did the same, but on Jetty. Additionally I cleared my browser's cache. The source tab works fine. Note that most of the Selenium WYSIWYG editor tests rely on the source tab and they all were passing before the 2.2M2 release,
odd. Why would the GWT servlet act differently in jetty or tomcat? I would understand it with static files but not the GWTservlet.
thus I think there is something particular to your installation that causes this problem. See http://code.google.com/webtoolkit/doc/1.6/DevGuideServerCommunication.html#D... . They say: "This most commonly occurs when a change to a service implementation is deployed to a server but out-of-date clients are still active." (in the browser cache maybe?)
No, definitely not, that installation is a fresh new domain. paul