Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 13:34
From version 12.1
edited by Bouke Reitsma
on 2023/03/03 14:12
Change comment: There is no comment for this version
To version 9.2
edited by Bouke Reitsma
on 2023/03/03 13:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Changing the default messaging format
1 +Changing the default messaging format to XML
Content
... ... @@ -20,11 +20,12 @@
20 20  
21 21  The last option allows you to switch between JSON or XML as your default messaging format in the gateway. In order to apply your new default to your project, you must press "Apply settings" in Design -> Architecture to confirm your change~*.
22 22  
23 -{{info}}~* Note Changing the default messaging format does not affect existing operations in Create. Migrating these flows requires a reset of the exit flow. Additionally, the default response in Catalog has to be changed to application/xml. {{/info}}
23 +{{info}}~* Note Changing the default messaging format does not affect existing operations in Create. Migrating these flows requires a reset of the exit flow. Additionally, the default response in Catalog has to be changed to application/xml.
24 + {{/info}}
24 24  
25 25  == 4. Impact in Create ==
26 26  
27 -The automatic flow creation in the Create phase is adapted to the new default setting. When changing the messaging format to XML, the components of newly generated flows are created with different names and settings. The image below shows an example of an API GET operation with XML as the default messaging format. Besides the changed naming of the transformation, no JSON factory support objects are required in your flow in comparison with a JSON messaging format.
28 +The automatic flow creation in the Create phase is adapted to the new default setting. When changing the messaging format to XML, the components of newly generated flows are created with different names and settings. The image below shows an example of an API GET operation with XML as the default messaging format. Besides the changed naming of the transformation, no support objects are required for this GET operation, since your gateway does not require a JSON response any more.
28 28  
29 29  [[image:Main.Images.Microlearning.WebHome@intermediate-api-management-changing-default-messaging-format--get-operation.png]]
30 30  
... ... @@ -41,7 +41,7 @@
41 41  
42 42  == 6. Suggested Additional Readings ==
43 43  
44 -If you are interested in this topic and want more information on it, please read the help text provided by eMagiz.
45 +If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
45 45  
46 46  == 7. Silent demonstration video ==
47 47