| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Axis2 properties allow you to configure the web services engine in the 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 |
Scope | axis2-client |
Description | Forces outgoing http/s messages to use HTTP 1.0 (instead of the default 1.1). |
setCharacterEncoding
Name | setCharacterEncoding |
|---|---|
Possible Values | false |
Default Behavior | By default character encoding is enabled in the ESB profile. |
Scope | axis2 |
Description | This property can be used to remove character encode. Note that if this property is set to 'false', the 'CHARACTER_SET_ENCODING' property cannot be used. |
Example | <property name="setCharacterEncoding" value="false" scope="axis2" type="STRING"/> |
...
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. Note that this property cannot be used if the 'setCharacterEncoding' property is set to 'false'. |
Example | <property name="CHARACTER_SET_ENCODING" value="UTF-8" scope="axis2" type="STRING"/> |
...
Name |
| ||
|---|---|---|---|
Possible Values | true | ||
Default Behavior | false | ||
Scope | axis2 | ||
Description | Remove cookie header from blocking request calls that passes through the HTTP HTTPS Servlet transport (for GET and POST HTTP methods). | ||
Example |
|