To be honest, whenever I start to have a less-than-perfect match between my entities and the content rendered in my client, I usually create DTOs. It's mildly annoying, but it results in a clean interface without a lot of extra payload (some of which might be security-sensitive) sent across the wire.
Jeff On Tue, Jun 28, 2011 at 8:26 AM, Drew Spencer <[email protected]> wrote: > Well I am just trying to get some kind of demo program running and learn > about cells/celltable while I go because my app needs to display lots of > tabular data and I understand this is the fastest way to do it. > What I am doing is this: > Get the supplies (List) > Loop the supplies, adding each supplier key to supplierList > Get the suppliers (Map) > add supplierName to each Supply (as a String) > Call setRowData for supplies > Like you say, this is ok for now, but I am wondering if there is a better > solution. At least this way I am updating every Supply record with the name > from the Supplier when it is accessed - that way if a Supplier Name does > change, it won't matter. > Drew > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine-java/-/bJevzjyvaLIJ. > 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-appengine-java?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-appengine-java?hl=en.
