You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I found this project very interesting for modelling.
I'd like to suggest an usefull improve:
In order to work with a huge amount of profiles, its necessary to distinguish them anyway other than name, so imagine I define my profile ejb3.0 and mix it in a project with the JUMP generated profile ejb3.0
Actually It's almost impossible, and the easiest way to achieve this is to define a URI for the generated profile, so this way could be possible to dintinguish to which profile the stereotype belongs to.
I am very interested in this upgrade because I'm involved in a code-generation tool, and think JUMP profiles are a good solution for handling psm annotations, but I need to distinguish between psm annotations that can be generated by the uml2java and other stereotypes that don't are annotations.
In your code
eu.artist.migration.modernization.uml2java.repackaged.gen.java.files.classJavaFile : genClassifierBody
generate all the stereotypes as annotations
If I'd like to override the eu.artist.migration.modernization.uml2java.repackaged.gen.java.services.stereotypeServices : genAnnotation
template, then I'd rather need this improvement.
the query aStereotype.profile.URI would be the easiest way, because all subpackages share the same profile with the same URI.
It can ve achieved with a simple QVTO or ATL. I could do this and ask for a commit, but I suppose you would like to decide the profile URI base.
Thanks for the attention,
Pere
The text was updated successfully, but these errors were encountered:
Hi,
I found this project very interesting for modelling.
I'd like to suggest an usefull improve:
In order to work with a huge amount of profiles, its necessary to distinguish them anyway other than name, so imagine I define my profile ejb3.0 and mix it in a project with the JUMP generated profile ejb3.0
Actually It's almost impossible, and the easiest way to achieve this is to define a URI for the generated profile, so this way could be possible to dintinguish to which profile the stereotype belongs to.
I am very interested in this upgrade because I'm involved in a code-generation tool, and think JUMP profiles are a good solution for handling psm annotations, but I need to distinguish between psm annotations that can be generated by the uml2java and other stereotypes that don't are annotations.
In your code
eu.artist.migration.modernization.uml2java.repackaged.gen.java.files.classJavaFile : genClassifierBody
generate all the stereotypes as annotations
If I'd like to override the eu.artist.migration.modernization.uml2java.repackaged.gen.java.services.stereotypeServices : genAnnotation
template, then I'd rather need this improvement.
the query aStereotype.profile.URI would be the easiest way, because all subpackages share the same profile with the same URI.
It can ve achieved with a simple QVTO or ATL. I could do this and ask for a commit, but I suppose you would like to decide the profile URI base.
Thanks for the attention,
Pere
The text was updated successfully, but these errors were encountered: