If I got you right, than, the first part of my first post comes up! Instead of declaring all your generics using Serializable object, you can just declare ( in the shared package ) all your possible combinaitons ( the whole veriety of all your non-trivial types ) and than, in your client-side code, you can safetly define objects of your types, and do not worry about serialization issues.
On 29 мар, 02:02, Ben Imp <benlee...@gmail.com> wrote: > The more generic your remote interface, the more code the GWT compiler > generates to try and handle all the possible values you may pass > through it. > > Having a method that can take something of type Serializable would, I > believe, make the GWT compiler generate code for all possible types, > since you can't get any more generic than that. > > -Ben > > On Mar 28, 3:58 pm, SergeZ <comp1...@gmail.com> wrote: > > > > > What it means ? Is it bad or not ? I see nothing bad or just nothing > > that takes my attention to that ! Can you explain your point about > > serialization policy in more details ? What did you mean ? > > > On 28 мар, 22:56, ciosbel <andrew...@gmail.com> wrote: > > > > Remember that gwt will create a serialization policy for all serializable > > > types at compile time. -- 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.
