Hi Arun, If the problem only happened on GWT's hosted browser, I would suggest you to change GWT 1.53 to GWT OOPHM branches. OOPHM can let you pick firefox or IE as hosted browser. I used it for a while and satisfied by it. The current build has also merged recent 1.53 release.
Kevin On Sun, Dec 21, 2008 at 11:59 AM, Kevin Tarn <kevn.t...@gmail.com> wrote: > I think it should not be the cache problem because the GWT's sample project > got the same result according to Arun. He should get into HTTP server to > find out what resource cannot be requested by HTTP server. HTTP 400 comes > from server, I don't think the result related to GWT's shell. > > Kevin > > > On Sun, Dec 21, 2008 at 11:43 AM, Ian Bambury <ianbamb...@gmail.com>wrote: > >> It could be a caching problem. This might be worth a try (if you get >> really desperate and you are convinced everything else is OK). >> Clear all temporary files from IE. >> Delete all the temporary files from the project (www, bin, tomcat) and >> from any other project if paranoid or if you have changed the package name >> recently to something you might have used before. >> Click on the project in Eclipse. Press F5, >> then do a project | clean. >> >> Ian >> >> >> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
