The one thing I've found useful is to make sure normal Servlets work first. You can get some test ones from TomCat's download I believe.
I say this because I found out with my specific web provider that in order for a servlet to work it had to have servlet in the path name. So I couldn't set an RPC entry point of "rpc/admin" it had to be "servlets/rpc/admin". Just something in that address had to say Servlets. This took me a long time to figure out and it was easier once I just used .jsp servlets from TOMCAT and took GWT out of the picture for a bit. That being said, make sure your web.xml has been uploaded correctly and all relative paths when uploaded to your server remained intact. Good luck! On Jul 13, 8:44 pm, Iain Bennett <[email protected]> wrote: > Hi Everyone, > I'm relatively new to GWT development and Java development so please > bear with me. It's been years since I've worked with RPC. > > I created a proof of concept test app at the following URL - in short > testing a date picker and testing the RPC communications as per the > basic test project that gets created when you create a new GWT project > in Eclipse. > > http://google.mathan.ca/BearsTouchPOC.html > > When testing through Eclipse, everything works. When I try running > the production version of the test site from my local computer (i.e. > run the html direct from the finder dropped into Safari or Chrome), or > via the URL above which is on hosted web provider, when I click the > send button I get an RPC error. > > Is there something I am not doing in the code, or maybe something not > installed that would need to be installed? > > Thanks again! I'm sure once I get through this I'll be set. > > -Iain -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
