Re: Class implements IsSerializable does not show up in all RPCRequest.serializationPolicy

Maybe the code snippet will helps.

Do you have default constructor for serialization purposes?
Is your custom exception listed in service method definition?

Peter

On 24. Júl, 17:34 h., citress <citr...@gmail.com> wrote:
> Hi,
>
> GWT version: 2.0.0
>
> My understanding of the serialization policy is that if a Class
> implements IsSerializable, it will be part of GWT's serialization
> policy whitelist. I created a custom, runtime  exception that
> implements IsSerializable. This runtime exception shows up in the
> serialization policy of one RPCRequest method, but not in another.
> Both methods do not declare the exception in their method
> declarations.
>
> Why can this exception be serialized in one RPC method call but not in
> another? Is implementing the IsSerializable interface alone not enough
> to make the class part of the serialization policy?
>
> Thanks in advance.

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.