Skip to content

Commit

Permalink
Merge pull request #7561 from Mariangela/patch-1
Browse files Browse the repository at this point in the history
[master] fixes #7556
  • Loading branch information
DinithiDiaz authored Jan 22, 2024
2 parents ab0d5ec + b6de7ff commit f8b4273
Showing 1 changed file with 6 additions and 6 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -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 `<MI_HOME>/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]]
Expand All @@ -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 `<MI_HOME>/conf` directory).

```toml
[[custom_message_builders]]
Expand Down Expand Up @@ -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]]
Expand Down Expand Up @@ -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 `<MI_HOME>/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]]
Expand Down

0 comments on commit f8b4273

Please sign in to comment.