E&S CVS Commit: PEAK - Removed code that checked for XMI.extension elements inside of places where

pje at eby-sarna.com pje at eby-sarna.com
Mon Dec 16 16:27:00 EST 2002


Module Name:	PEAK
Committed By:	pje
Date:		Mon Dec 16 21:26:01 UTC 2002

Modified Files:
	PEAK/src/peak/storage: xmi.py

Log Message:
Removed code that checked for XMI.extension elements inside of places where
the XMI specs don't say they're allowed to be.  Apparently, the only valid
places for extensions are in the XMI.extensions section, in the top level
XMI.contents section, and the top level of individual object instances.

Also, updated to-do notes re: XMI 1.2 and a little about XMI 2.0.  1.2
looks even easier to implement fully than 1.1, but of course there are few
tools that go past 1.1.  XMI 2.0 is supported by EMF (Eclipse Modelling
Framework) which makes very nice GUI editors with tree and table views.
It would be really nifty if we could use it to edit PEAK models and data,
but I've got to learn a lot more about XMI 2.0 first.


To view diffs of this commit, you can use the following URL(s):
http://cvs.eby-sarna.com/PEAK/src/peak/storage/xmi.py.diff?r1=1.6&r2=1.7

To generate a diff of this commit:
cvs rdiff -r1.6 -r1.7 PEAK/src/peak/storage/xmi.py

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.




More information about the source-changes mailing list