Ease the DSE solution converter handling
The DSE soulution converter is hard to use: It is unclear when to use the copy operation, very specific utility methods have to be used, hidden dependencies between converters are easily introduced.
- Replace the many input parameters of the transform(…) call with a single POJO. This object can then encapsulate the existing utility methods to enforce a defined fetching strategy. Moreover, the copy logic of objects might be abstractable there.
- Evaluate whether the CopyRefMap could be used more extensively: Copies created within a transformator are recorded there. Thus, they could be reused to fetch child artifacts of primary atrifacts. Nevertheless, this option has to be carefully analyzed w.r.t. to the above point, since child elements are already present there.
- Copying all inputs incl. input ModelSnapshots may be alternative to operate on copies that crossreference each other correctly from the beginning.
(from redmine: issue id 3791, created on 2019-08-07, closed on 2019-11-08)
- Error with test 1 and 2
- 3791-test3.txt Error with test 3