Hi Lex, The main problem comes from enhancement added fields, so user can add @GwtTransient annotation on it. Yes, enhancement is evil, but we have to do with them...
Regards Bruno On 19 juin, 17:09, Lex Spoon <[email protected]> wrote: > On Mon, Jun 15, 2009 at 11:59 AM, noon<[email protected]> wrote: > > > Hello, > > > This thread follows this one (http://groups.google.com/group/Google- > > Web-Toolkit-Contributors/msg/582cfe33f17deab3), so please read it > > before this one. > > > To make Google App Engine and GWT work together (in adapter4appengine > > project), I had to modify theRPCserialization code. > > My first goal was to add *clean extension points*, to allow any third > > library developer to tuneRPCserialization according to his needs. Of > > course, I used it to develop a DataNucleus adapter, and plan to port > > Hibernate one as well. > > > The idea is to allow 2 kinds of extension points : > > - ISerializationFilter, that indicates if a specific field of a > > class should be serialized or not. It is called for serialization > > signature computation and for each object serialization > > * Typical use : used to remove new fields from enhancement > > - ISerializationTransformer, that can change a object instance > > from one type to another one > > * Typical use : used to turn persistent collection back to > > regular one > > Are you familiar with the transient keyword and the @GwtTransient > annotation? These let you respectively eliminate a field from > serialization, and eliminate a field from GWT serialization. > > -Lex --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
