Closed eclipse-ocl-bot closed 1 month ago
By Christian Damus on Apr 25, 2007 09:29
I'll have to study the impact on the code before I can commit to changing the behaviour of getOwningClassifier() in this milestone. I expect it'll be OK, because it seems to be intended to work this way.
Note that this probably isn't just a problem for the OCL standard types (in the Ecore binding), but also for the OCL-defined additional attributes and operations in both Ecore and UML bindings.
By Christian Damus on May 03, 2007 09:24
Updated getOwningClassifier in the UMLReflection implementation for Ecore and UML, to look for a shadowed classifier, in the case of both operations and attributes.
By Nick Boldt on Jan 28, 2008 16:37
Move to verified as per bug 206558.
By Ed Willink on May 27, 2011 02:40
Closing after over a year in verified state.
By Ed Willink on May 27, 2011 02:42
Closing after over a year in verified state.
| --- | --- | | Bugzilla Link | 183996 | | Status | CLOSED FIXED | | Importance | P3 normal | | Reported | Apr 25, 2007 09:21 EDT | | Modified | May 27, 2011 02:42 EDT | | Version | 1.1.0 | | Reporter | Sergey Boyko |
Description
For the addition operations defined e.g. on OclAny their real parent is\ OclAny_Class. And org.eclipse.ocl.utilities.UMLReflection::getOwningClassifier() returns just it while OclAny is expected.\ On the other hand org.eclipse.ocl.ecore.internal.OCLStandardLibraryImpl::getOwner() returns correct parent for such operation.
Seems that getOwningClassifier() should also resolve shadowed parent like getOwner() does.