Maybe I was not clear about it: 1) We do not "map anything together" from the model at client side and the best is: we do not need to; our (GWT) RPC returns one instance of our domain model containing all references among elements like the way we designed them, it's just that easy... the referencing between the elements is persisted and loaded by hibernate, just like the elements are
2) We don't do that... each model object is represented by its own view object Regarding your "few points": 1) Why is it different? It's simply model based... Andreas On 13 Jul., 20:44, munna kaka <[email protected]> wrote: > Thanks A. > 2 more selfish questions > 1) In your case after simply loading various model objects via RPC do you > again map them togather ? > 2) If one of model object is used (read-only) by two different MVP widgets > than how do you share that model object. > > Few points > 1) I understand that your proj domain is different from anybody else > 2) I do have coarse grained GWT RPC calls but I need to make fine grained > calls now > > On Tue, Jul 13, 2010 at 12:11 PM, andreas > <[email protected]>wrote: > > > > > Are you sure you mean 'client side mapping'? > > > What I understand from it is you have a domain model with classes > > (customer, order, item) which somehow reference each other. > > > How do you retrieve instances of these classes from your application > > backend? Are instances of these classes referencing each other at all, > > for example before being persisted or after being retrieved from a > > database? > > > If you use hibernate you can persist the associations between domain > > model classes as well (see hibernate documentation) and of course load > > it again as well. Now if you break up these associations and retrieve > > each classes instances separately I'd suggest your associations are > > lost, but why would you do something like that? > > > Get your model instance out of your database and pass it to the client > > at once. For example request one CUSTOMER which references some ORDERs > > which reference some ITEMs. GWT RPC will not break up these > > references. > > > If you have a very large database things are getting different of > > course because you do not want to load the whole database because all > > entries references cover the whole database. Then you'll want to > > consider other fetching strategies. > > > We are working with (quite) complex domain models containing > > hierarchies and references as well. In our case we will not load the > > whole database by accident and simply loading via RPC works great. > > > Hope this help... > > > Andreas > > > On 13 Jul., 19:55, mk <[email protected]> wrote: > > > How do you maintain mapping between Model objects at client browser? > > > > Say for example, over the course of user conversation, there were > > > three DIFFERENT ajax calls to load CUSTOMER, ORDERS and ITEMS. > > > > Now do you manually map CUSTOMER to ORDER and ORDER to ITEM in client > > > to maintain mapping between Model objects.. > > > ( or do you store CUSTOMER, ORDER, ITEM separatly with no mapping or > > > there is a framework like hibernate mappings but for browser which > > > maps model objects with configuration) > > > > thanks > > > -- > > 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]<google-web-toolkit%2Bunsubs > > [email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-web-toolkit?hl=en. -- 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.
