OCL defined operations and properties presist across Environments

[eclipse-ocl-bot]

| --- | --- | | Bugzilla Link | 154371 | | Status | CLOSED FIXED | | Importance | P2 normal | | Reported | Aug 18, 2006 12:30 EDT | | Modified | May 27, 2011 02:41 EDT | | Version | 1.0.0 | | Reporter | Christian Vogt |

Description

Additional operations and properties defined using OCL are stroed in an adapter on the owner EClassifier. This allows subsequent OCL expressions to make use of them. These additional operation and properties are also present if the OCL expression is evaluated using different Environments.

Should these additional operations and properties only be accessible if used within the same Environment used when they were defined?

[eclipse-ocl-bot]

By Christian Damus on Jan 08, 2007 13:36

The J2SE 5.0 (bug 156361) and UML Metamodel support (bug 163808) enhancements are changing the way that additional operations and properties are managed; they will be scoped to the environment, not global.

[eclipse-ocl-bot]

By Christian Damus on Jan 26, 2007 16:56

The new org.eclipse.ocl.OCL API retains separate definitions of additional attributes and operations, effectively creating isolated OCL environments. These additional features are no longer attached to the model elements.

[eclipse-ocl-bot]

By Nick Boldt on Jan 28, 2008 16:36

Move to verified as per bug 206558.

[eclipse-ocl-bot]

By Ed Willink on May 27, 2011 02:39

Closing after over a year in verified state.

[eclipse-ocl-bot]

By Ed Willink on May 27, 2011 02:41

Closing after over a year in verified state.