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
I am encountering an issue in Eclipse while using Sirius for modeling with SysML. Specifically, when using the Sirius-provided Create Tool in the tree view to create certain elements, I am receiving an error message immediately after clicking to create the following elements:
UseCaseDefinition
UseCaseUsage
AnalysisCaseUsage
VerificationDefinition
VerificationUsage
In contrast, creating sysml::PartUsage under the same conditions works without any issues. This discrepancy has left me uncertain about what could be causing the error for these specific elements.
Error Description
Each time I attempt to create one of the above elements, an error message appears (as shown in the attached screenshot). Unfortunately, the error log mentions "Cannot modify resource set without a write transaction," which suggests that the creation process for these elements may not be happening within a necessary write transaction.
Steps to Reproduce
Open the Sirius model in Eclipse.
Navigate to the tree view and use the Create Tool to attempt to add any of the problematic elements.
Observe the error message appearing after creation.
Additional Context
Since sysml::PartUsage works perfectly in the same context, I am curious if there might be something unique about these elements, such as a different initialization requirement or specific dependencies, that might require additional handling. I have checked my configurations but have not identified any significant differences.
Could you advise on why these elements might be prompting this error, and how I might adjust the configuration or transaction handling to support their creation? Any guidance or insight would be greatly appreciated, as I would like to ensure that these elements integrate seamlessly with the rest of the model.
Thank you very much for your time and assistance, and please let me know if any additional details are required to investigate this issue further.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Dear Sirius Development Team,
I am encountering an issue in Eclipse while using Sirius for modeling with SysML. Specifically, when using the Sirius-provided Create Tool in the tree view to create certain elements, I am receiving an error message immediately after clicking to create the following elements:
UseCaseDefinition
UseCaseUsage
AnalysisCaseUsage
VerificationDefinition
VerificationUsage
In contrast, creating sysml::PartUsage under the same conditions works without any issues. This discrepancy has left me uncertain about what could be causing the error for these specific elements.
Error Description
Each time I attempt to create one of the above elements, an error message appears (as shown in the attached screenshot). Unfortunately, the error log mentions "Cannot modify resource set without a write transaction," which suggests that the creation process for these elements may not be happening within a necessary write transaction.
Steps to Reproduce
Open the Sirius model in Eclipse.
Navigate to the tree view and use the Create Tool to attempt to add any of the problematic elements.
Observe the error message appearing after creation.
Additional Context
Since sysml::PartUsage works perfectly in the same context, I am curious if there might be something unique about these elements, such as a different initialization requirement or specific dependencies, that might require additional handling. I have checked my configurations but have not identified any significant differences.
Could you advise on why these elements might be prompting this error, and how I might adjust the configuration or transaction handling to support their creation? Any guidance or insight would be greatly appreciated, as I would like to ensure that these elements integrate seamlessly with the rest of the model.
Thank you very much for your time and assistance, and please let me know if any additional details are required to investigate this issue further.
Best regards,
hoajie
Beta Was this translation helpful? Give feedback.
All reactions