I would not recommend either use GWT serialization or JVM serialization to store in a file, it isn't the main purpose. First, don't trust that GWT never change Serialization method in the future. Second, JVM serialization use serialversionuid to check if the .class is compatible and the version of JVM (a class serializate with 1.5 is not compatible with 1.6).
I recomend use XML o JSON to store class. There are a lots of frameworks around to do this job. Juan 2011/3/24 Kroc <vincent.legen...@gmail.com> > any ideas or advises ? > > > On 23 mar, 14:04, Kroc <vincent.legen...@gmail.com> wrote: > > I've serialized data with standard java way into files and database. > > As I'm dicovering RPC.encodeResponseForSuccess to inject data in web > > pages, > > I wondered to know if it's safe to store GWT serialized data into > > files and blobs > > for future use (either on client and server side) ? > > > > And if yes, is gwt (de)serialization procedure slower than stadard > > java serialization ? > > -- > 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 > google-web-toolkit+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- 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 google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
