On 7 nov, 00:46, Jack <[email protected]> wrote: > Oh that sounds pretty nice. Haven't realized that its possible that > way.. hehe..and its not nasty at all :) > I'll give it a try. Thanks! > > And a second question that comes to my mind: > When using RequestFactory our domain objects are only defined by > interfaces. Is there a class in the framework that posts some sort of > PropertyChangeEvent on the provided EventBus whenever a property is > changed on client-side (This event should be fired whenever a setter > method is called on client side). If not is there a way to integrate > such a feature?
On each setter call, no (this is because a RequestContext is a kind of "transaction": it accumulates changes to entity proxies and method calls on the RequestContext –currently limited to a single method call AFAIK– to later send them all in one go to the server when you call fire()). When the server responds, it tells the client to fire EntityProxyChange events on the event bus, those are the ones you'll listen to to update the rest of your app. At least this is how I understand how it's supposed to be! -- 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.
