Commit 08564bb9 authored by Philip Makedonski's avatar Philip Makedonski
Browse files

+ added know issues in readme

parent b3726fa3
......@@ -119,4 +119,12 @@ The TDL mapping to TTCN-3 relies on some functionalities from [TRex2 / T3Tools](
https://t3tools.informatik.uni-goettingen.de/downloads/trex2/
After installation, to apply the transformation of a TDL model into TTCN-3 code, open the TDL model (making sure it is selected) and press the `T3` icon on the toolbar. This shall result in the generation of a `.ttcn3` file with the same name in the same folder as the model.
\ No newline at end of file
After installation, to apply the transformation of a TDL model into TTCN-3 code, open the TDL model (making sure it is selected) and press the `T3` icon on the toolbar. This shall result in the generation of a `.ttcn3` file with the same name in the same folder as the model.
## Known Issues
* The implementation of the OCL constraints validation may occasionally fail to identify all constraint violations or even display an error message. This is likely due to caching issues and should be resolved by restarting Eclipse. Possible solutions to this issue are being investigated.
* The implementation of the TTCN-3 transformation may occasionally fail, likely due to caching issues, and should be resolved by restarting Eclipse. Possible solutions to this issue are being investigated.
* The implementation of the TTCN-3 transformation is not 100% complete. While it provides a sufficient framework for constructing the main elements of a TTCN-3 specification, some elements are not yet fully supported (ProcedureCalls, some DataUses, some Behaviours). Please report any parts than are urgently needed so that future releases could provide support for them with a higher priority.
* The translation between the different representations (textual formats, XF) as well as using the different repersentations during the importing of data definitions in TDL may have some limitations. While using XF as a target format should work in practically all cases, using the legacy textual representations (`.tdlan2` and `.tplan2`) as targets in particular may fail due to some compatibility issues. The standardised TX textual representations should work in most cases and are the recommended target textual representation formats. However, the formatting may not be ideal in some cases. This may cause syntax errors in the indentation-based format in particular as it depends on correct formatting to determine the corresponding syntax structures. Please report any issues with corresponding examples.
* The importing of data definitions from OpenAPI and ASN.1 relies on third-party components, thus problems with processing the OpenAPI / ASN.1 specifications due to the third-party components will likely result in incomplete importing of the data definitions.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment