Skip to Content
Last modified by dfirdausy on 2024/09/18 13:34
From version 13.1
edited by etorken
on 2023/08/23 12:52
Change comment: There is no comment for this version
To version 11.1
edited by BoukeReitsma
on 2023/03/03 13:17
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.etorken
1 +XWiki.BoukeReitsma
Content
... ... @@ -24,7 +24,7 @@
24 24  
25 25  == 4. Impact in Create ==
26 26  
27 -After the flows are resetted in Create, 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.
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 28  
29 29  [[image:Main.Images.Microlearning.WebHome@intermediate-api-management-changing-default-messaging-format--get-operation.png]]
30 30