Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide ability to recognize attribute inheritance by the OCL parser #9

Closed
eclipse-ocl-bot opened this issue Sep 18, 2024 · 2 comments

Comments

@eclipse-ocl-bot
Copy link
Collaborator

| --- | --- |
| Bugzilla Link | 113884 |
| Status | CLOSED INVALID |
| Importance | P2 enhancement |
| Reported | Oct 26, 2005 15:50 EDT |
| Modified | May 27, 2011 02:47 EDT |
| Version | 1.0.0 |
| Reporter | Vishy Ramaswamy |

Description

If you have a class "Super" with an attribute "size" and a subclass "Sub"
(i.e. class "Sub" inherits via generalization from "Super"), then an OCL
constraint on "Sub" will not recognize the attribute "size".

@eclipse-ocl-bot
Copy link
Collaborator Author

By Christian Damus on Dec 20, 2005 09:40

This cannot be a defect in the OCL parser for EMF. EAttributes are always inherited and Ecore does not define any "visibility" mechanism that could interfere with inheritance.

Because OCL is defined by the UML specification, I am speculating that perhaps the reporter has implemented a custom Environment for UML (which does have a "private" visibility for non-inherited attributes) that makes only a UML class's visible attributes accessible in the corresponding Ecore classifier?

@eclipse-ocl-bot
Copy link
Collaborator Author

By Ed Willink on May 27, 2011 02:47

Closing after over 18 months in resolved state.

This was referenced Sep 19, 2024
This was referenced Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant