Skip to Content
Last modified by Danniar Firdausy on 2024/09/16 14:32
From version 6.1
edited by Erik Bakker
on 2024/03/07 15:21
Change comment: There is no comment for this version
To version 5.1
edited by Eva Torken
on 2023/08/08 17:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.etorken
Content
... ... @@ -20,8 +20,6 @@
20 20  
21 21  * Imported files cannot be larger than 1MB
22 22  * xs:all statements cannot be represented in the data model.
23 -* ref statements cannot be represented in the data model.
24 -* choice constructs cannot be represented in the data model.
25 25  * Iterations (maxOccurs) over a threshold of 50 are not accepted
26 26  * Cross reference between entities that could lead to an infinite loop are not accepted
27 27  
... ... @@ -32,9 +32,7 @@
32 32  Identifying and knowing about these restrictions will improve your decision making the moment you want to import your definition
33 33  
34 34  * Imported files cannot be larger than 1MB
35 -* xs:all statements cannot be represented in the data model.
36 -* ref statements cannot be represented in the data model.
37 -* choice constructs cannot be represented in the data model.
33 +* xs:all statements cannot be represented in the data model
38 38  * Iterations (maxOccurs) over a threshold of 50 are not accepted
39 39  * Cross reference between entities that could lead to an infinite loop are not accepted
40 40  
... ... @@ -53,19 +53,11 @@
53 53  * Write a custom XSLT that will transform the incoming message to a structured messages that you can validate via the tooling
54 54  * Use a custom XSD as validation and use the standard eMagiz tooling for your transformation, whereby you assume that your system definition has a defined structure
55 55  
56 -=== 3.3 ref statements cannot be represented in the data model ===
52 +=== 3.3 Iterations (maxOccurs) over a threshold of 50 are not accepted ===
57 57  
58 -As specified before in earlier microlearnings, eMagiz defines the expected structure with the help of data models. Within a data model you need to specify the association between entities. In XSD terminology this is represented as follows <xs:element type="itemsType" name="items"/>. However, sometimes we see a different notation that is not working when importing an XSD in eMagiz. This notation is <xs:group ref="status_group" />. To get this in you need to rewrite the association in your XSD a bit to reflect the first notation and mention that the assocation is optional (minOccurs="0").
59 -
60 -=== 3.4 Choice statements cannot be represented in the data model ===
61 -
62 -As specified before in earlier microlearnings, eMagiz defines the expected structure with the help of data models. Within a data model you need to specify the association between entities and order within these entities. In XSD terminology this is represented as follows <xs:complexType><xs:element name="employee" type="employee"/><xs:element name="member" type="member"/></xs:complexType>. However, sometimes we see that a choice is offered in the XSD. This notation means that you can supply A or B. This notation is <xs:complexType><xs:choice><xs:element name="employee" type="employee"/><xs:element name="member" type="member"/></xs:choice></xs:complexType>. To get this in you need to remove the reference to the <xs:choice> and the </xs:choice> lines in your XSD and make each element within the choice optional (minOccurs="0").
63 -
64 -=== 3.5 Iterations (maxOccurs) over a threshold of 50 are not accepted ===
65 -
66 66  To prevent weird results when it comes to the creation of data models we do not accept maxOccurs above 50. To succesfully import your definition you should change the maxOccurs setting to unbounded. This way eMagiz will succesfully import the definition. As of today we have never encountered a practical case where this caused issues.
67 67  
68 -=== 3.6 Cross reference between entities that could lead to an infinite loop are not accepted ===
56 +=== 3.4 Cross reference between entities that could lead to an infinite loop are not accepted ===
69 69  
70 70  In some cases we see definitions in which entities keep referecing each other. This could cause an infinite loop to occur when trying to build up the correct structure of your system message. Therefore we do an initial check when importing your file to safeguard ourselves against creating infinite loops in our portal that will in the end break the eMagiz portal.
71 71  
... ... @@ -74,9 +74,7 @@
74 74  Identifying and knowing about these restrictions will improve your decision making the moment you want to import your definition
75 75  
76 76  * Imported files cannot be larger than 1MB
77 -* xs:all statements cannot be represented in the data model.
78 -* ref statements cannot be represented in the data model.
79 -* choice constructs cannot be represented in the data model.
65 +* xs:all statements cannot be represented in the data model
80 80  * Iterations (maxOccurs) over a threshold of 50 are not accepted
81 81  * Cross reference between entities that could lead to an infinite loop are not accepted
82 82