Changes for page Changing the default message format
Last modified by Danniar Firdausy on 2024/09/18 13:34
From version 7.1
edited by Bouke Reitsma
on 2023/03/02 08:48
on 2023/03/02 08:48
Change comment:
There is no comment for this version
To version 5.1
edited by Bouke Reitsma
on 2023/03/01 09:27
on 2023/03/01 09:27
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -18,13 +18,13 @@ 18 18 19 19 AFBEELDING 1 TOEVOEGEN 20 20 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 ~*.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 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.{{/info}} 24 24 25 25 == 4. Impact in Create == 26 26 27 -The automatic flow creation in the Create phase is adapted tothenew default setting. When changing the messaging format to XML, the components of newly generated flows arecreatedwithdifferentnamesand settings. The image below shows anxampleofan API GET operationwith 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.27 +The automatic flow creation in the Create phase is updated to incorporate these changes. When changing the messaging format to XML, the components of newly generated flows are adapted to the changes. The image below shows the changed flow when building an API GET operation. 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 AFBEELDING 2 TOEVOEGEN 30 30