| Persisting diagram in rdb [message #78846] |
Mon, 20 November 2006 08:12 |
Eclipse User |
|
|
|
Hi,
I am looking at persisting the diagram itself.
I am encountering some difficulties because of the way the persistentChildren
efeature of View is handled.
Although this efeature exists in the ecore model it is renamed at runtime to
'children'. It is this line (1853) in NotationPackageImpl:
initEReference(getView_PersistedChildren(), this.getNode(), null, "children",
null, 0, -1, View.class, !IS_TRANSIENT, !IS_VOLATILE, IS_CHANGEABLE,
IS_COMPOSITE, !IS_RESOLVE_PROXIES, !IS_UNSETTABLE, IS_UNIQUE, !IS_DERIVED,
IS_ORDERED); //$NON-NLS-1$
Is there a specific reason to rename this efeature (just curious here)?
Would it be logical to instead of renaming the efeature persistedchildren to
add children as an additional efeature (volatile/transient)?
gr. Martin
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
Powered by
FUDForum. Page generated in 0.13671 seconds
Home