I don't think there is a way to distinguish them, therefore I think their usefulness is extremely limited. I would recommend simply using application-specific events for the purposes you are describing. If there is a way to distinguish them somehow, I would appreciate it if someone could lend some advice, because I'm just not seeing it.
On Friday, September 16, 2011 1:58:24 PM UTC-4, tom wrote: > > Hello, > > in my app, I've got a tree that displays data for my EntityProxies. Now > when an EntityProxy is updated, I'd like to update the data shown in the > tree. For this, I've implemented an EntityProxyChange handler that is then > registered for the type of EntityProxies I want to handle the updates for. > > This works fine. Every time I persist my EntityProxies, an > EntityProxyChangeEvent with an UPDATE WriteOperation is fired and it ends > up in my handler. > > The problem is that the handler is also notified when the tree loads the > data (every time a new node is expanded). I guess this happens because > seeing an EntityProxy for the first time is also an EntityProxyChangeEvent > with an UPDATE WriteOperation. > > How can I distinguish these two different events? > > regards > > Tom > > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
