That should be fine. Serializable objects don't have to be trivial and
the system is fairly robust. It's hard to break gwt serialization
(although you can - for example see
http://code.google.com/p/google-web-toolkit/issues/detail?id=3577)
BTW - if you put your DTOs in a "client" package, that means your server
code must access that package too. I prefer to define a separate package
for shared server & client code, and keep "client" strictly for code
that is only used client-side
Thomas Holmes wrote:
> I am working on a test GWT_RPC application. I have Hibernate POJO's
> that use annotations, and I have declared those in the Spring 2.5.6
> applicationContext xml file.
>
> So, I also created a bunch of DTO POJO's, and my question is ... do
> these RPC POJO's need to be VERY basic, or can they be compound
> objects. For example, I have the following:
>
> webapp.client.dto.ADTO
> webapp.client.dto.BDTO
> webapp.client.dto.TestDTO
>
> public class TestDTO implements Serializable {
>
> private int id;
> private String name;
> private Date date;
> private ADTO a;
> private BDTO c;
>
> ... public getters/setters ...
> }
>
> Will this be ok to define? A and B DTO might also be a compound
> objects, but they still ALL live under the client umbrella.
>
> Thanks!
> Tom
> >
>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
