|Re: proxy resolution problem [message #619756]
||Wed, 06 June 2007 13:28
Originally posted by: cdamus.ca.ibm.com|
Are these objects UML Properties? (the term "role" suggests so) The UML
metamodel made a change just prior to the 2.1 M7 milestone, in which the
ConnectorEnd::role <--> ConnectableElement::end association is no longer
bidirectional, but directed from ConnectorEnd to ConnectableElement.
I think the UML2 implementation should be using its inverse-referencing
CacheAdapter to make the resolved O1 know the same role as the proxy.
I have replied to UML2 newsgroup for somebody there to comment further ...
Laurent Le Goff wrote:
> We have found a strange thing related to EMF2.1 proxies and
> inter-resources references. We have two Objects O1 and O2. There is a
> bidir relation between these two.
> O1 <-role1--------role2-> O2
> Both objects are stored on different resource files R1 and R2. When O1 is
> loaded from R1, object O2 is not loaded but replaced by a proxy O2' which
> behaves like O2. Particularily, its role1 is O1. Later when the O2' proxy
> is resolved, it appears that the corresponding O2 element is effectively
> loaded from R2, but unfortunatelly, its role1 is null.
> Note that role1 is defined transient in O2 and thus is missing in R2.
> Is it normal for the resolved objet O2 to have a different role1 than
> its proxy O2' ?
> We have locally bugfixed this behavior by using a specific
> ModificationTrackingAdapter attached to our resources. Is that a good
> idea/use of the ResourceTracking mechanism ?
> Sam et Laurent
Powered by FUDForum
. Page generated in 0.01511 seconds