Some Validation Rules are not executed properly within the generated plugin. [message #1785602] |
Tue, 17 April 2018 08:00  |
Eclipse User |
|
|
|
Hello fellow modelers,
I am relatively new to Sirius. To date I have created the design tool I wanted for my meta-model using Sirius and it works flawlessly within the runtime environment. All the validation rules I included work as intended as well.
However, when I export it as plugin and use the plugin instead, some validation rules seem to either not get executed at all or their evaluation is not correct.
I have narrowed down the issue to two categories. To explain them let me introduce you to the structure of my meta-model. It has a root element lets call it R. This R element contains any number of some other element A. That element A is inherited by many other elements, Ai.
So for the validation rules that I have selected any of the Ai elements as the Target Class, everything works fine in both environments. The validation rules for the A element are evaluated wrong in the plugin environment, while they are evaluated correctly in runtime environment. The validation rules for the root element R are evaluated properly in the runtime environment but it seems like they are completely ignored in the plugin environment.
Are there any clues on why this is the case? Is this possibly a bug? In case you need some more specific information please let me know.
I am using Sirius 5.1 on Oxygen.1 Release (4.7.1) on a Mac.
Thanks in advance for your time and your effort!
Christoforos.
|
|
|
|
|
|
|
|
|
|
Re: Some Validation Rules are not executed properly within the generated plugin. [message #1786950 is a reply to message #1786792] |
Wed, 16 May 2018 05:54  |
Eclipse User |
|
|
|
Hello Pierre,
based on your question on how I integrated my plugin, I tried it to a fresh Eclipse Oxygen copy and it seems to work fine.
So I suppose that there must be some sort of conflict when the plugin is installed in the "development" Eclipse (where there exist also the corresponding Ecore/Sirius projects in the same workspace) or that something was misconfigured. I write this here so anyone in future will have this possibility also in mind once such issues occur.
Since the plugin works as intended in non development eclipse environments, I consider this issue solved, as far as I am concerned.
Therefore, thank you a lot for your time and any related effort from your part. In case I spot any related issue I will let you know.
Regards,
Christoforos
[Updated on: Wed, 16 May 2018 05:55] by Moderator
|
|
|
Powered by
FUDForum. Page generated in 0.04818 seconds