Yes, it's not UML specific.
Ansgar
On 10/05/2010 01:44 PM, Tristan FAURE wrote:
Okay i understand better.
Just to be sure i assume what you do is in the backbone and it is not
dependent of UML, isn't it ?
Regards
Tristan FAURE
Le 05/10/2010 11:45, Ansgar Radermacher a écrit :
Hi Tristan,
an additional remark: on the EObject level, references to imported
models appear in the eCrossReference list. I just wanted to remark that
I initially thought that the resources belonging to cross-referenced
objects were not part of the resource set, since I did not see them
immediately after loading with the debugger - until I realized that the
cross-references were pointing to proxy object's that were resolved on
demand and the resources appear in this moment. I did not make any
changes in the on-demand policy, it was primarly a remark that I had
not been aware initially that referenced models appear in the resource
set. The fact that they appear once resolved made the task a lot
simpler.
Currently, I explicitly unload resources of referenced models if the
underlying OS resource (File) has changed. Thus, the referenced objects
become proxys again and will be resolved on demand (by the existing,
unmodified on-demand load mechanism) with the updated contents.
Ansgar
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
--
Ansgar Radermacher CEA/DRT/DILS/LISE
http://www-list.cea.fr/index.htm
http://www2.cs.unibw.de/alumni/Ansgar/
phone: +33 16908 3812
mailto: ansgar.radermacher@xxxxxx
|
