Sure, that works. Locator eliminates the need for static methods in the entity. Can you elaborate on what you mean by matching for getters / setters in the Locator?
/dmc On Mon, Mar 7, 2011 at 3:51 PM, koma <[email protected]> wrote: > > I was thinking about adding parameter List<EmailAddress> to persist : > > *public String persist(ContactEntry contactEntry) { ... }* > > would become : > > *public String persist(ContactEntry contactEntry, List<EmailAddress> > emailAddresses) { ... }* > > and take care of the linking in one go. > It would be great if ContactEntryProxy would also try to match for > getters/setters in its locator. Typically, you use a Locator if you don't > control all aspects of the underlying entity anyway. Or don't I see this > correct ? > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > 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. > -- David Chandler Developer Programs Engineer, Google Web Toolkit w: http://code.google.com/ b: http://googlewebtoolkit.blogspot.com/ t: @googledevtools -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
