The server expects the client to tell it where the file should be, and the client reports that the file should be in the same directory as its .nocache.js file - we call that the "base directory" of a gwt application.
RemoteServiceServlet.getSerializationPolicy is responsible for looking this up, based on the incoming request, and the expected name of the generated file (according to the client). If using SDM and a port provided as I mentioned, this method will defer to getCodeServerPolicyUrl() if no policy file was found on the server itself. Otherwise, you'll see the warning you mentioned. On Wednesday, December 18, 2024 at 4:45:23 PM UTC-6 [email protected] wrote: > <[email protected]> wrote: > >> You're triggering the LegacySerializationPolicy... we should make that >> clearer when it happens. >> >> This occurs when your <hash>.gwt.rpc policy file wasn't present on the >> server (or wasnt at the expected path). Legacy serialization is much more >> strict in what it will accept. >> > > I saw a warning about that in the log but not know what it meant. > I am serving the client side files from Apache and the server side files > from Tomcat so they are separate. > > Where does the server side code expect the .gwt.rpc file to be? > >> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/619a5fbf-ea0b-4528-99f2-38a7836ee330n%40googlegroups.com.
