if its not too much data, you can use autobeans to serialize your data
class and store the stuff in a cookie or the url itself. i've been doing
something similar, just with a selfmade serialization mechanism instead
of the autoproxy one.
Am 26.07.2012 08:14, schrieb Rubina:
> Hi All,
> We have one requirement to implement in GWT application. Below example
> will clear the requirement –
> There are 3 screensin application. Suppose, useris on 2ndscreen after
> moving from 1^st screen to 2ndscreen. When user clicks on Next button on
> first screen, then some RPC call is executed and fetch data from some
> external database. This data is used to display on 2^nd screen. Now user
> bookmarks the browser URL (2^nd screen) and closes the browser window.
> Next time, now user directly wants to navigate to the 2^nd screen
> without repeating the work done on 1^st screen. We want to store the
> state of 2^nd screen somehow on browser. If this screen launches, all
> Next and Previous button should also work properly.
> Is this requirement achievable, if yes then which GWT APIs provides this
> feature? Please advice.
> You received this message because you are subscribed to the Google
> Groups "Google Web Toolkit" group.
> To view this discussion on the web visit
> To post to this group, send email to email@example.com.
> To unsubscribe from this group, send email to
> For more options, visit this group at
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to email@example.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.