Hi,
http://code.google.com/events/io/sessions/GoogleWebToolkitBestPractices.html
AFAIK DTO should not be composed.
HIH
On Tue, Sep 22, 2009 at 11:06 PM, Thomas Holmes
<thomas.j.hol...@gmail.com>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
> >
>
--
A coward is incapable of exhibiting love; it is the prerogative of the
brave.
--
Mohandas Gandhi
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
