if I understood the tomcat security-manager right, it would be no problem to turn it off, if your app runs on your own dedicated server. on the other hand, if you host serveral apps that you have no control over, you should not turn it off.
On 1 Dez., 21:57, bradrover <brk...@gmail.com> wrote: > I have a GWT application that makes some server side web service calls > to a Spring web service on the same machine (Ubuntu 9.04 and Tomcat > 6). > > I've spent countless hours trying to get security to allow these calls > to go through in my GWT application. Finally, after all of that, I now > have gwt rpc serialization errors for types I am not even trying to > serialize: > > SEVERE: Exception while dispatching incoming RPC call > com.google.gwt.user.client.rpc.SerializationException: Type > 'java.util.PropertyPermission' was not included in the set of types > which can be serialized by this SerializationPolicy or its Class > object could not be loaded. For security purposes, this type will not > be serialized. > > I had already added a similar class to my gwt.rpc file for a previous > error. Why do I have to do this? At this point I I am tempted to just > turn off tomcat security. All I want to do is have my GWT application > be able to make a server side web service call, which works perfectly > on my local Windows XP machine. -- 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-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
