|Re: Profile definition results in dangling references when using a model library [message #1834238 is a reply to message #1834212]
||Thu, 05 November 2020 13:24
|| vincent lorenzo
Registered: June 2010
Location: Paris Saclay, France
Hi Jonas, |
to my mind, it is a mistake to declare the Datatype in the library because at the model level, it won't be a reference to the datatype but it will be an instance of it.
So when you declare it in a library, I think the corresponding EClass is not created for it during the profile definition and you get an error.
When you declare the same Datatype directly in the profile, there is no problem.
Nevertheless, maybe your design is allowed and it is a UML2 bug.
Please, ask this question on UML2 forum to get a precise answer.
Powered by FUDForum
. Page generated in 0.02370 seconds