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

Allow aspects to be top-level entities #1521

TimLethbridge opened this issue Jan 14, 2020 · 0 comments

Allow aspects to be top-level entities #1521

TimLethbridge opened this issue Jan 14, 2020 · 0 comments


Copy link

@TimLethbridge TimLethbridge commented Jan 14, 2020

Aspects in Umple currently must be embedded in classes and operate on matching methods in that class.

It should be possible to specify a before or after statement at the top level of an Umple program. That would take an extra parameter which would be a pattern of matching classes.

When encountered, such an option would simply copy apply the statement in all matching classes at the metamodel level. This should not require any new code generation, since the existing code generation for aspects should work. All types of aspects should work include generated methods, user-defined methods; and with or without patterns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.