Changes for page Changing the default message format
Last modified by Danniar Firdausy on 2024/09/18 13:34
From version 9.2
edited by Bouke Reitsma
on 2023/03/03 13:13
on 2023/03/03 13:13
Change comment:
There is no comment for this version
To version 10.1
edited by Bouke Reitsma
on 2023/03/03 13:17
on 2023/03/03 13:17
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -25,7 +25,7 @@ 25 25 26 26 == 4. Impact in Create == 27 27 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,sinceyourgatewaydoesnotrequirea JSONresponseanymore.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 JSON factory support objects are required in your flow in comparison with a JSON messaging format. 29 29 30 30 [[image:Main.Images.Microlearning.WebHome@intermediate-api-management-changing-default-messaging-format--get-operation.png]] 31 31 ... ... @@ -42,7 +42,7 @@ 42 42 43 43 == 6. Suggested Additional Readings == 44 44 45 -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. 46 46 47 47 == 7. Silent demonstration video == 48 48