I want to avoid having to use DTOs for transferring my Users with RPC. Basically I have a number of rpc calls for my users, and based on the configuration and the user rights, etc... there is a number of fields I want to hide. My approach has been to create DTOs for each case. I was now thinking of using the JPA relationships and lazy loading instead. For instance I store additional information (bio, etc...) in an "Additional" object, with a onetoone relationship and lazy loading. So I guess based on the call I just need to load the field or not, instead of filling up a dedicated DTO each time I send a User with "holes".
Does that make sense? any one has cons on this idea? will RPC send empty fields or will it be more clever and just not add the fields that are null? Thanks, Thomas -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/iLFbBNp8rLAJ. 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.
