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
Objects may be created using multiple strategies which can create incompatible objects in a single model #1591
Milestone
Comments
sbegaudeau
added
type: bug
difficulty: medium
area: backend
package: domain
and removed
area: backend
labels
Jan 19, 2023
Example stack trace (to make it easier to search for the issue):
|
mcharfadi
added a commit
to mcharfadi/sirius-components
that referenced
this issue
Feb 23, 2023
…ate incompatible objects in a single model Bug: eclipse-sirius#1591 Signed-off-by: Michaël Charfadi <michael.charfadi@obeosoft.com>
39 tasks
39 tasks
sbegaudeau
pushed a commit
to mcharfadi/sirius-components
that referenced
this issue
Feb 27, 2023
…ate incompatible objects in a single model Bug: eclipse-sirius#1591 Signed-off-by: Michaël Charfadi <michael.charfadi@obeosoft.com>
sbegaudeau
pushed a commit
that referenced
this issue
Feb 27, 2023
…ate incompatible objects in a single model Bug: #1591 Signed-off-by: Michaël Charfadi <michael.charfadi@obeosoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When we are creating the root objects of a resource, we are loading on the fly the EPackages from scratch without considering existing EPackages loaded in the package registry of the editing domain.
When we are creating objects using a dedicated tool from the view DSL with some model operations, they are created using the EPackages available in the package registry of the editing domain.
Let's consider a click on
New Operational Entity
which comes with a dedicated node tool using the view DSL.As a result, it is quite easy to create a model in which the root object and objects created using the view DSL do not share the same EPackage. For some reason, this does not seems to create any issue in my case.
The problem becomes obvious since, when we are creating objects using the view DSL thanks to a canonical tool, the EPackage used is the EPackage of
self
and thus the source of the metamodel to use may change depending on the target of the tool.Let's consider a click on
New Operational Actor
which rely on the canonical behavior.Now we will end up with two subgraphs of objects in our domain using the same concepts from two versions of our EPackage.
The text was updated successfully, but these errors were encountered: