| Models with multipe files and only file reference - preferred approach EVL [message #1853927] |
Sun, 24 July 2022 08:15  |
 Glatz Martin
Messages: 23
Registered: March 2016 |
Junior Member |
|
|
Hello,
I'm having the following situation.
My CAEX model can be built up by an unlimited number of files. The link between the files is an element "External reference" which defines an alias and the (relative) path to the referenced file.
Example:
Main file: Testcase.aml
Testcase.aml references ./RefFolder/ReferecedLib.aml (alias ReferencedLib)
ReferecedLib.aml references ./RefFolder/DeepModel.aml (alias DeepModel)
(for simplicity, I've attached the file structure).
The problem is, that I can't navigate via the External reference, as it contains only alias and Path to the referenced Model artefact.
I see two options, and would like to know, which one you would prefer (especially in the context, that the model is based on an official standard):
1. I could easily extend the meta model with a reference to the concrete referenced file content - while transforming the .aml Files to .xmi, (in java) I would read the xmi file and set the reference.
2. During tranforming of the .aml Files to .xmi, I build up a Map (Alias -> CAEXFile Content) and push this map to the EVL context.
From an implementation point of view, the first variant looks nicer to me, but I'm not sure if it is recommended to extend the meta model of a industry standard, to make evaluation easier.
What do you think?
Best regards
Martin
|
|
|
|
Powered by
FUDForum. Page generated in 0.03011 seconds
] 
Search
Help
Register
Login
Home
