Replies: 1 comment
-
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
I'm facing a new challenge after successfully implementing a fix for model loading in Sirius Web and I need some guidance.
Initially, I ran into the classic "Package with uri '...' not found" error when trying to upload an Ecore model. The root cause was that the Ecore package was not registered in the server's ResourceSet.
I successfully fixed this problem by following the approach in a related discussion thread:#3682 . Now, my model.ecore loads correctly into the Sirius Web explorer.
While the model loads, I can't seem to do anything with it in terms of visualization. The Sirius Viewpoint features are not active for the uploaded Ecore model.
Specifically:
When I select the uploaded Ecore model, I do not see the "Create representation" option in the explorer or the context menu.
In other parts of the application (like when configuring a Viewpoint or selecting a domain for an object), the uploaded Ecore metamodel is not available for selection.
My current fix only involves registering the EcorePackage.eINSTANCE in the PackageRegistry of the ResourceSet.
Does this approach—which enables model loading—inhibit the creation of Sirius Viewpoints/Representations? Or, is there an additional technical step I need to take to bridge the gap between a successfully loaded Ecore model and its use as a domain for a Sirius Viewpoint (.odesign) in the Web environment?
Any insights on how to properly integrate the uploaded Ecore metamodel so it can be used for representation creation would be greatly appreciated! Thank you in advance.
Beta Was this translation helpful? Give feedback.
All reactions