We are using RPC.encodeResponseForSuccess() in our code to serialize GWT objects and include them in the page (avoiding an extra round trip and simplifying startup logic in some cases).
This is a bit awkward as this (the only public) API requires passing a serialization policy, which changes every time our API changes. We can load the generated policy ".gwt.rpc" file with SerializationPolicyLoader.loadFromStream() easily enough, however this file has a strong hash name and therefore we cannot automate this step in our build. Now, I'm aware that we could probably create a linker to accomplish this. But I'm wondering what I'm missing here. The docs imply that we don't need a policy if we use IsSerializable, but I thought that this was being deprecated. Or we could create a no-op policy that accepts everything, but I am not sure of all of the security implications of that. Can anyone tell me how they manage this issue? thanks, Pat --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
