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.

Sign up for GitHub

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

Jump to bottom

Stereotype resolution isn't quite correct #16

Closed
seidewitz opened this issue May 16, 2016 · 1 comment
Closed

Stereotype resolution isn't quite correct #16

seidewitz opened this issue May 16, 2016 · 1 comment
Assignees
@seidewitz
Labels
bug
Milestone
Alf RI v1.0.4

Comments

@seidewitz
Copy link
Contributor

seidewitz commented May 16, 2016 •
edited
Loading

Currently, stereotype resolution is implemented to find stereotypes that are directly owned by explicitly applied profiles, or that are owned by nested packages of those profiles, but not nested profiles. However, the UML 2.5 specification (which is clearer than the UML 2.4.1 spec), says that "Applying a Profile means recursively applying all its nested and imported Profiles. Stereotypes that are public members of a Profile may be applied to applicable model elements in Packages to which the Profile has been applied." Such implicit profile application should be implemented properly in the stereotype resolution algorithm for Alf.
@seidewitz seidewitz added the bug label May 16, 2016
@seidewitz seidewitz added this to the Alf RI v1.0.2 milestone May 16, 2016
@seidewitz seidewitz self-assigned this May 24, 2016
seidewitz added a commit that referenced this issue Sep 1, 2016
@seidewitz
Issue #16 - Added nested profiles to computed set of applied profiles.
950d4f6 
- Also corrected error in InternalElementReferenceImpl.getMembers.
@seidewitz
Copy link
Contributor Author

Resolved in v1.0.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@seidewitz seidewitz

Labels
bug
Projects
None yet
Milestone
Alf RI v1.0.4
Development

No branches or pull requests
1 participant
@seidewitz