Modeling your views based on your domains/entities can give you some headaches. In this case you can simple use a @Transient value, but if it grows, create a new object to handle these 2 entities.
You could even replicate the supplier name to make it easier and less RPC calls. But if your supplier can change name, you would need to update all Supply related to it. On Tue, Jun 28, 2011 at 11:44 AM, Drew Spencer <[email protected]>wrote: > Thanks for the info, Bruno. > > So you are saying I need a kind of proxy entity that wraps the needed data > from both objects? I think I may need a custom cell after doing a little > more reading. There must be a simple way. > > Also I think I should have posted this in the GWT group. :/ > > -- > 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/-/ei0ikt_ldN4J. > > 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. > -- Bruno Fuster -- 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.
