hi Jesper, any access modifier for the constructor can be used. This is documented and I tested id.
http://code.google.com/intl/en/webtoolkit/doc/latest/DevGuideServerCommunication.html#DevGuideSerializableTypes > 「Serializable User-defined Classes」 > … > 3. As of GWT 1.5, it must have a default (zero argument) constructor (with > any access modifier) or no constructor at all. Paul, I think I cannot serialize Throwable, but you can do that with IsSerializable. I want to know the service method you define. http://code.google.com/intl/en/webtoolkit/doc/latest/FAQ_Server.html#Does_the_GWT_RPC_system_support_the_use_of_java.io.Serializable > Another important point to note is that none of the classes that implement > java.io.Serializable in the full Java JRE implement java.io.Serializable in > GWT's emulated JRE. > What this means is that types that implement java.io.Serializable in the JRE > like Throwable, or StackTraceElement won't be able to transfer across the > wire through GWT RPC since the client won't be able to serialize/deserialize > them. -- bufferings
-- 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.
