|
Re: Coevolution with an existing project & Rule used twice in the same bridge. [message #1772587 is a reply to message #1772499] |
Tue, 12 September 2017 16:49 |
Olivier Constant Messages: 106 Registered: January 2012 |
Senior Member |
|
|
Hello Aurélien,
1. The CapellaIntermediateUpdateScope is necessary only because in the case of Capella, a model contains a lot of predefined elements (architectures, root functions, default data types, ...) that usually need to be ignored. A transformation that targets a Capella model usually focuses on specific subsets of the Capella model, not the whole. The scope allows restricting the update to such subsets. You do not need to worry about that if you are not in such a case.
2. In a bridge, every instance of a rule or query must have a unique identifier for unambiguous traceability. So if you have several instances of the same query/rule class, they cannot share a common (hence static) ID. The solution you found is the correct one. This is, btw, why the Query and Rule classes have constructors with ID parameters.
Hope this helps.
|
|
|
Powered by
FUDForum. Page generated in 0.03700 seconds