Problem with EntityProxyChange handling

[tom]

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

[JahSon]

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.

[Thomas Broyer]

On Friday, February 8, 2013 7:55:44 PM UTC+1, JahSon wrote:

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.

It was suggested (a long time ago, just like this thread) to use a Set or Map of the EntityProxyId-s you've already seen; if you've never seen the EntityProxyId for a given EntityProxyChange+UPDATE then it means it's a "new" proxy (at least from your widget's PoV).

I otherwise concur that their usefulness is (very?) limited.