Have you read what Jamie told you? He gave you a hint - your relative paths are wrong (TamperData or Firebug will tell you what they are), that's all. Either fix your Tomcat config or put the resources where they should be.
Or even better, use GWT 1.6 which has a far better deployment strategy. On Sun, May 24, 2009 at 10:41 AM, Donald.W.Long < donald.w.l...@thelongsfamily.com> wrote: > > What I have done, is made the URL fully qualified and it works. > > But seems to me it should work with not being fully qualified. > > Has anyone ever deployed GWT on tomcat with local html pages loaded > via a Frame? > > Thanks > > On May 22, 9:51 am, Jamie <jamiesharbor-sou...@yahoo.com> wrote: > > I would suggest using Firefox + TamperData. > > > > Then you should be able to see what URL the browser is trying to > > access when you use the relative URL, or if in fact it is sending the > > request at all. > > > > Jamie. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
