Hi Adam. When looking in the source of RemoteServiceServlet you'll find the following comment in the doGetSerializationPolicy method:
/* * Check that the module path must be in the same web app as the servlet * itself. If you need to implement a scheme different than this, override * this method. */ So I'll guess this behaviuor was the intention of the authors. So as the comment recommends you are free to subclass RemoteServiceServlet and override doGetSerializationPolicy and you'll be free to use any source to load the policy from that is accessible for a servlet. On 16 Sep., 02:00, adam <[EMAIL PROTECTED]> wrote: > My new app is at foo.com and my static content is all served from > static.foo.com. GWT stuff is served from static.foo.com/gwt. > RemoteServiceServlet#doGetSerializationPolicy wants to find > my .gwt.rpc file in the gwt directory relative to the servlet. Was > this the intention of the authors? Shouldn't it be trying to get > my .gwt.rpc file from static.foo.com/gwt? Do I have to make a gwt > directory in my web app folder especially for this purpose? It seems > kind of awkward to do that. Maybe, at the very least, it should look > for the .gwt.rpc folder in "/" instead of using new > URL(moduleBaseURL).getPath() iff the moduleBaseURL host is different > than the servlet host. > > If the current behavior wasn't the intention of the authors, then I > don't mind submitting a patch with unit tests. > > Thank you, > Adam --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
