eclipse-ocl-bot
commented
13 hours ago By Christian Damus on May 04, 2007 20:52
Updated OCL.uml to no longer mark the TypeType::referredType feature as transient.\ Regenerated OCL.ecore and the org.eclipse.ocl plug-in.\ Regenerated org.eclipse.ocl.ecore and org.eclipse.ocl.uml plug-ins.
Any other clients extending either the generic OCL model or either of the Ecore/UML bindings will have to regenerate to pick up the TypeType change. This should be OK, as UML's namespace URI change and EMF's codegen template changes to fix generics bugs are all coming next week, so these regenerations would be necessary anyway (OCL will still have to regenerate everything again next week, too).
| --- | --- | | Bugzilla Link | 183494 | | Status | CLOSED FIXED | | Importance | P3 normal | | Reported | Apr 21, 2007 03:14 EDT | | Modified | May 27, 2011 02:41 EDT | | Reporter | Ed Willink |
Description
OCL 11.3.2 defines OclType as the singleton instance of TypeType.
However TypeType.referredType is a transient attribute supporting multiple TypeTypes. As a transient serialisation results in redundant TypeType elements without the referredType to distinguish them.
It seems that either TypeResolver should not create per-classifier TypeTypes as per the OCL spec, or that the distinction between them should be non-transient as per a richer implementation.