| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Axis2 properties allow you to configure the web services engine in the ESBthe ESB profile, such as specifying how to cache JMS objects, setting the minimum and maximum threads for consuming messages, and forcing outgoing HTTP/S messages to use HTTP 1.0. You can access some of these properties through the Property mediator with the scope set to axis2 or axis2-client as shown below.
...
Name | FORCE_HTTP_1.0 |
|---|---|
Possible Values | true/false |
Default Behavior | |
Scope | axis2-client |
Description | Forces outgoing http/s messages to use HTTP 1.0 (instead of the default 1.1). |
Example |
CHARACTER_SET_ENCODING
Name | CHARACTER_SET_ENCODING |
|---|---|
Possible Values | Any valid encoding standard (E.g., UTF-8, UTF-16 etc.) |
Default Behavior | N/A |
Scope | axis2 |
Description | Specifies the encoding type used for the content of the files processed by the transport. |
Example | <property name="CHARACTER_SET_ENCODING" value="UTF-8" scope="axis2" type="STRING"/> |
DECODE_MULTIPART_DATA
Name | DECODE_MULTIPART_DATA |
|---|---|
Possible Values | true, false |
Default Behavior | false |
Scope | axis2 |
Description | Specifies whether to decode multipart messages when the message is built in a content aware mediation scenario. Otherwise, the outgoing message will be in the encoded form. |
Example | <property name="DECODE_MULTIPART_DATA" value="true" scope="axis2" action="set" type="BOOLEAN"/> |