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

ElementFactory.interfaceForName should handle all UML metaclasses #74

Open
seidewitz opened this issue Apr 3, 2019 · 1 comment
Open

ElementFactory.interfaceForName should handle all UML metaclasses #74

seidewitz opened this issue Apr 3, 2019 · 1 comment
Assignees
@seidewitz
Labels
bug

Comments

@seidewitz
Copy link
Contributor

The ElementFactory.interfaceForName method is used to get a class object for the wrapper interface named UML metaclass. However, since interfaceForName is static, it only looks for interfaces in the statically known org.modeldriven.alf.uml package, which does not cover all UML metaclasses. If there is no interface for the named metaclass, the method returns null. This is not adequate when the reference implementation is integrated into a tool that implements the complete UML metamodel.
@seidewitz seidewitz self-assigned this Apr 3, 2019
@seidewitz seidewitz added the bug label Apr 3, 2019
@seidewitz
Copy link
Contributor Author

The easiest, though somewhat brute force, way to handle this would be to just generate interfaces that cover the entire UML metamodel.

@abstratt abstratt mentioned this issue May 28, 2020
Draft
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
No milestone
Development

No branches or pull requests
2 participants
@abstratt @seidewitz