I found the problem! I think the root cause comes from a pair of things. First off, I had a pair of GWT-servlet.jar in my deployment. One inside my WAR and one in the server lib. The one in the server lib was from 1.5.1 and the one in deployment was 1.5.2. I removed the older JAR.
The second thing was a misconfiguration of my Services inside my gwt.xml file. I was using a munged web.xml to define the services at the root (aka, http:./localhost:8888/LoginService ) when I needed to be using the service present at the GWT Hosted level (http://localhost: 8888/Application.gxt.xml/LoginService.) This misconfiguration was causing a disconnect in my application as the RPC service was looking for the serialization policy in the wrong path. Hopefully if anyone else runs into this issue you can check these two things. Thanks, Evan On Nov 18, 3:36 pm, Evan Ruff <[EMAIL PROTECTED]> wrote: > Hey guys, sorry to be such a bother, but does anyone have any idea how > to fix this problem? > > I'm starting to get Serialization errors and I'm not sure if they're > legit or if it is a symptom of my bigger problem. > > Thanks for any tips! > > E > > On Nov 18, 7:59 am, Evan Ruff <[EMAIL PROTECTED]> wrote: > > > Oh hey, sorry to mention my environment. I'm running Eclipse 3.1 with > > Cypal Studio. I've got GWT 1.5.2. The application has always been on > > 1.5.0 or better, so I don't think I have any outstanding annotation > > issues or such. > > > Thanks! > > > On Nov 17, 12:47 pm, Evan Ruff <[EMAIL PROTECTED]> wrote: > > > > Hey Guys, > > > > I'm having some trouble with my GWT project. I'm getting some weird > > > errors and I think it's related to either my project setup, my gwt.xml > > > files or something of that nature. I'm running in hosted mode with the > > > embedded Tomcat. > > > > Basically, I'm getting a couple of weird errors. First off, when I'm > > > trying to set my path for my servlet (defined plainly in web.xml as > > > <url-pattern>/LoginService</url-pattern>) I can't find it using either > > > GWT.getHostPageBaseURL () or GWT.getModuleBaseURL(). I think it is > > > because both paths resolve > > > to:http://localhost:8888/com.teledini.app.Application/ > > > . In the past, I thought that one call would give > > > me:http://localhost:8888/ > > > . I worked around this problem by statically setting the path, but > > > that's suboptimal, as I ALWAYS forget to change it when I deploy :-). > > > > The second problem, I believe, is symptomatic of the first. I get "The > > > serialization policy file '/com.teledini.app.Application/ > > > 15CBC2E263CDF186FC35F31569112349.gwt.rpc' was not found; did you > > > forget to include it in this deployment?" when attempting to Serialize > > > my RemoteServiceServlet return. In my compiled output, the file is > > > there and is correctly named, but it can't seem to find it. I believe > > > that this is causing me the dreaded "This application is out of date, > > > please refresh your browser" error when deployed. > > > > My project has several modules with dependency, but I have other > > > projects that are similarly structured without problems. Am I just > > > making a stupid mistake or what else can I check? I'm a little stuck > > > with my application as is and really appreciate some advice. > > > > Thanks! > > > > Evan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
