Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 325059 - Add an option for the OCLinEcore Editor to support the implicit Rootclass EObject for each class to provide access to eContainer() functions etc.
Summary: Add an option for the OCLinEcore Editor to support the implicit Rootclass EOb...
Status: CLOSED WONTFIX
Alias: None
Product: OCL
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: OCL Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-12 16:24 EDT by Simon harrer CLA
Modified: 2012-05-29 13:23 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon harrer CLA 2010-09-12 16:24:06 EDT 
Build Identifier: 20100617-1415

I would like to use the functions eContainer() and other that can be activated normally by defining EObject as the implicit root class. Is it possible to define an option to enable this feature for the OCLinEcore editor?

Reproducible: Always
Comment 1 Ed Willink CLA 2010-09-13 09:42:35 EDT 
The availability of eContainer() was really a bug since it has no OMG OCL foundation.

The intention (Bug 283052) is to support reflection in OCL so that container() works and the result behaves coherently as a Class not an EClass.

This should ensure that OCL is to users consistently UML-aligned, even though the underlying tooling is Ecore-based.
Comment 2 Ed Willink CLA 2011-05-27 02:58:00 EDT 
Closing WONTFIXes.
Comment 3 Ed Willink CLA 2012-05-29 13:23:27 EDT 
Closing all bugs resolved in Indigo.