Notifications emf vs. cdo [message #481399] |
Thu, 20 August 2009 19:49 |
|
Hi,
i have a questing for CDONotifications. Move and remove cdoNotifications
are differing from emfNotifications.
If i am using an emfEdit moveCommand the newValue of the notification is
the moved EObject.
On commiting the cdoTransaction a CdoNotification is sent to the other
clients. But in this case, the newValue is null. I had a look at the
source code and it is not resolved there.
Maybe i have to keep attention by resolving the newValue myself.
I am using the changeSubscriptionPolicy(CDOAdapterPolicy.ALL).
Has anybody an idea, why cdo does not resolve the moved EObject and does
not put it into the new value of the notification?
Thanks in advance,
Flo
|
|
|
Re: Notifications emf vs. cdo [message #481404 is a reply to message #481399] |
Thu, 20 August 2009 20:00 |
|
Flo,
What do you mean by "resolve"?
It's eventually just a bug in the CDODeltaNotification (probably not in
the CDOProtocol itself) that the value is not set. Simon can possibly
shed light on this...
Cheers
/Eike
----
http://thegordian.blogspot.com
Florian Pirchner schrieb:
> Hi,
>
> i have a questing for CDONotifications. Move and remove
> cdoNotifications are differing from emfNotifications.
>
> If i am using an emfEdit moveCommand the newValue of the notification
> is the moved EObject. On commiting the cdoTransaction a
> CdoNotification is sent to the other clients. But in this case, the
> newValue is null. I had a look at the source code and it is not
> resolved there.
>
> Maybe i have to keep attention by resolving the newValue myself.
>
> I am using the changeSubscriptionPolicy(CDOAdapterPolicy.ALL).
>
> Has anybody an idea, why cdo does not resolve the moved EObject and
> does not put it into the new value of the notification?
>
> Thanks in advance,
> Flo
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
|
Re: Notifications emf vs. cdo [message #481447 is a reply to message #481419] |
Fri, 21 August 2009 05:45 |
|
Hi simon, hi eike,
i think that it not so easy to determine the influenced objects for some
events in cdo, because they do not exist anymore, when cdo creates the
change notification. Specially for removes.
In the case of a remove notfication i would expect the removed eObject in
the oldValue of the notification and the container of the removed object
as the notifier.
Do i have to use the revision to get the removed object? I think so. What
do you think?
For move operations i have already resolved the oldObject myself, because
it is still existing inside the same parent container. The notifier,
feature and position are enough to get the influenced object.
For my purpose it is absoultly important to have access to the oldObjects.
Redview uses these informations to change the swt ui by passing them to
the ui controllers.
It would be really great, if you can point me a way how to access the
removed object. I am not sure what is the best practice in cdo? Currently
the revision seams to be best way of doing so.
Lots of Thanks, Flo
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04091 seconds