Martin, The RPC serialization generator is most likely being run before your custom generator. As a result serialization code, whitelisting, etc... are not being created. Unfortunately there is no way of guaranteeing that your generator is run before the RPC serialization generator.
That said, I did have a couple of thought: 1. Within your RPCs, what class is your server expecting? 2. Rather than generate classes that you send across the wire, would it be possible to send an interface, and generate client-side classes that understand how to instantiate themselves based on said interface? 2010/1/11 Martin Söderström <[email protected]> > Hi, > > I have a custom Generator (subclassing > com.google.gwt.core.ext.Generator) class that generates a class to be > used as argument in an RPC method. The generated class implements > Serializable and the interface that the RPC method expects. This used > to work in GWT 1.7, but with GWT 2.0 I get a > com.google.gwt.user.client.rpc.SerializationException. Using > IsSerializable instead of Serializable does not make any difference. > > It feels like, in GWT 2.0, the scanning for RPC serializable classes > does not take into consideration the custom generated classes. Does > anyone know anything about this? A possible workaround? > > /Martin > > -- > 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]<google-web-toolkit%[email protected]> > . > 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 [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.
