The option to call the next RPC event in the onSuccess() of the previous one is a good way to achieve this. But the option KevMo gives is actually better if possible.
On Dec 14, 10:27 pm, KevMo <[email protected]> wrote: > Have you tried making an RPC that returns A, B, & C at the same time? > > On Dec 14, 10:55 am, Mike Dee <[email protected]> wrote: > > > > > > > > > What is a preferable way to do multiple gwt-rpc calls to setup a UI? > > In particular, we have a view that requires several successive calls > > (order is important) to the database to setup. This is necessary > > because there is a stateful part to our app. For example, first we > > have to load A and once we have A we can then load B and C. > > > What I've been doing is to start the chain of events in the view's > > onLoad. I make a call to load A. The handler for it then kicks off > > loading B and C, in onSuccess(). > > > Is this a good way to go about doing this? Opinions appreciated. -- 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.
