Our GWT application, when build on Solaris (we develop on Solaris), compiles without error and works fine when deployed to a Tomcat server (on Solaris too).
When we use the 'Hosted Mode' shell, we run it on Windows (as there isn't a Solaris version yet) with -noserver and the URL pointing to the Solaris Tomcat server. The shell has access to the source code through a mapped drive to the Solaris box. What we noticed is that the files generated by the Solaris build process and when pressing the Compile button in the shell are different. That kills us when we do RPC calls as the Serialization Policy files can not be found. As a work around we implement IsSerializable instead of java.io.Serializable such that we can use the LegacySerializationPolicy on the server. Why is that happening? Well, the files generated on Windows contain /r/ n as line separator and on Solaris it's just /n. That makes the file content different as far as MD5 is concerned even though the files are really identical otherwise. I checked that by manually calculating the MD5 for the files generated on Windows and Solaris - the MD5 checksum matches the file name of the files. Can that be somehow addressed at the compiler level? Is there another workaround? Thanks Christian --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
