From b6de7fffdf860df8b03f0ae9a1845296f462ee3f Mon Sep 17 00:00:00 2001 From: Mariangela Hills Date: Sat, 13 Jan 2024 21:18:43 +0100 Subject: [PATCH] Update message-builders-and-formatters.md --- .../message-builders-and-formatters.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/en/docs/install-and-setup/setup/mi-setup/message_builders_formatters/message-builders-and-formatters.md b/en/docs/install-and-setup/setup/mi-setup/message_builders_formatters/message-builders-and-formatters.md index cdbedb1fa9..57fd40d9f6 100644 --- a/en/docs/install-and-setup/setup/mi-setup/message_builders_formatters/message-builders-and-formatters.md +++ b/en/docs/install-and-setup/setup/mi-setup/message_builders_formatters/message-builders-and-formatters.md @@ -54,11 +54,11 @@ application_binary = "org.apache.axis2.format.BinaryFormatter" ### Handling message relay -If you want to enable message relay, so that messages of a specific content type are not built or formatted but simply pass through the Micro Integrator, you can specify the message relay builder (for the required content types) in the deployment.toml file (stored in the `MI_HOME/conf` directory) as shown below. +If you want to enable message relay, so that messages of a specific content type are not built or formatted but simply pass through the Micro Integrator, you can specify the message relay builder (for the required content types) in the `deployment.toml` file (stored in the `/conf` directory) as shown below. ```toml [[custom_message_formatters]] -class = "org.wso2.carbon.relay.BinaryRelayBuilder" +class = "org.wso2.carbon.relay.ExpandingMessageFormatter" content_type = "application/json/badgerfish" [[custom_message_builders]] @@ -70,7 +70,7 @@ See [Configuring Message Relay]({{base_path}}/install-and-setup/setup/mi-setup/m ### Handling messages with no content type -To ensure that messages with no content type are handled gracefully, add the following to the deployment.toml file (stored in the `MI_HOME/conf` directory). +To ensure that messages with no content type are handled gracefully, add the following to the `deployment.toml` file (stored in the `/conf` directory). ```toml [[custom_message_builders]] @@ -131,7 +131,7 @@ com.ctc.wstx.outputInvalidCharHandler.char=\u0020 ### Validating JSON messages -If you want the JSON builder to validate JSON messages that are received by the Micro Integrator, the following property should be added to the deployment.toml file. This validation ensures that erroneous JSON messages are rejected by the Micro Integrator. +If you want the JSON builder to validate JSON messages that are received by the Micro Integrator, the following property should be added to the `deployment.toml` file. This validation ensures that erroneous JSON messages are rejected by the Micro Integrator. ```toml [[transport.http]] @@ -213,10 +213,10 @@ processed in the WSO2 Micro Integrator mediation flow. ``` 2. Create a JAR file of this class and add it into the classpath of the - Axis2 installation, i.e., the `MI_HOME/lib` + Axis2 installation, i.e., the `/lib` folder. 3. To enable your custom message builder for content type text/xml, add - the following line in the deployment.toml file: + the following line in the `deployment.toml` file: ```toml [[custom_message_builders]]