Given below is a list of the generic properties.
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
PRESERVE_WS_ADDRESSING
Name | PRESERVE_WS_ADDRESSING | ||
---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | none | ||
Scope | synapse | ||
Description | By default, the ESB adds a new set of WS-Addressing headers to the messages forwarded from the ESB. If this property is set to " | ||
Example |
|
RESPONSE
Name | RESPONSE | ||
---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | none | ||
Scope | synapse | ||
Description | Once this property is set to 'true' on a message, the ESB will start treating it as a response message. It is generally used to route a request message back to its source as the response. | ||
Example |
|
OUT_ONLY
Name | OUT_ONLY | ||
---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | none | ||
Scope | synapse | ||
Description | Set this property to "true" on a message to indicate that no response message is expected for it once it is forwarded from the ESB. In other words, the ESB will do an out-only invocation with such messages. It is very important to set this property on messages that are involved in out-only invocations to prevent the ESB from registering unnecessary callbacks for response handling and eventually running out of memory. | ||
Example |
|
ERROR_CODE
Name | ERROR_CODE | ||
---|---|---|---|
Possible Values | string | ||
Default Behavior | none | ||
Scope | synapse | ||
Description | Use this property to set a custom error code on a message which can be later processed by a Synapse fault handler. If the Synapse encounters an error during mediation or routing, this property will be automatically populated. | ||
Example |
|
ERROR_MESSAGE
Name | ERROR_MESSAGE | ||
---|---|---|---|
Possible Values | string | ||
Default Behavior | none | ||
Scope | synapse | ||
Description | Use this property to set a custom error message on a message which can be later processed by a Synapse fault handler. If the Synapse encounters an error during mediation or routing, this property will be automatically populated. | ||
Example |
|
ERROR_DETAIL
Name | ERROR_DETAIL | ||
---|---|---|---|
Possible Values | string | ||
Default Behavior | none | ||
Scope | synapse | ||
Description | Use this property to set the exception stacktrace in case of an error. If the ESB encounters an error during mediation or routing, this property will be automatically populated. | ||
Example |
|
ERROR_EXCEPTION
Name | ERROR_EXCEPTION |
---|---|
Possible Values | java.lang.Exception |
Default Behavior | none |
Scope | synapse |
Description | Contains the actual exception thrown in case of a runtime error. |
TRANSPORT_HEADERS
Name | TRANSPORT_HEADERS | ||||||||
---|---|---|---|---|---|---|---|---|---|
Possible Values | java.util.Map | ||||||||
Default Behavior | Populated with the transport headers of the incoming request. | ||||||||
Scope | axis2 | ||||||||
Description | Contains the map of transport headers. Automatically populated. Individual values of this map can be accessed using the property mediator in the transport scope. | ||||||||
Example |
|
messageType
Name | messageType | ||
---|---|---|---|
Possible Values | string | ||
Default Behavior | Content type of incoming request. | ||
Scope | axis2 | ||
Description | Message formatter is selected based on this property. This property should have the content type, such as text/xml, application/xml, or application/json. | ||
Example |
|
ContentType
Name | ContentType | ||
---|---|---|---|
Possible Values | string | ||
Default Behavior | Value of the Content-type header of the incoming request. | ||
Scope | axis2 | ||
Description | This property will be in effect only if the messageType property is set. If the messageType is set, the value of Content-Type HTTP header of the outgoing request will be chosen based on this property. Note that this property is required to be set only if the message formatter seeks it in the message formatter implementation. | ||
Example |
|
disableAddressingForOutMessages
Name | disableAddressingForOutMessages | ||
---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | false | ||
Scope | axis2 | ||
Description | Set this property to "true" if you do not want the ESB to add WS-Addressing headers to outgoing messages. This property can affect messages sent to backend services as well as the responses routed back to clients. | ||
Example |
|
ClientApiNonBlocking Anchor Blocking Blocking
Blocking | |
Blocking |
Name | ClientApiNonBlocking |
---|---|
Possible Values | "true", "false" |
Default Behavior | true |
Scope | axis2 |
Description | By default, Axis2 |
spawns a new thread to handle each outgoing message. |
This property holds the primary thread until a VFS proxy writes to a VFS endpoint. You need to remove this property from the message |
to change this behavior when queuing transports like JMS are involved. | |||
Example |
|
---|
transportNonBlocking
Name | transportNonBlocking | ||
---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | true | ||
Scope | axis2 | ||
Description | This property works the same way as | ||
Example |
|
TRANSPORT_IN_NAME
Name | TRANSPORT_IN_NAME | ||
---|---|---|---|
Scope | synapse | ||
Description | Mediation logic can read incoming transport name using this property (since WSO2 ESB 4.7.0) | ||
Example |
|
preserveProcessedHeaders
Name | preserveProcessedHeaders | ||
---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | Preserving SOAP headers | ||
Scope | synapse(default) | ||
Description | By default, Synapse removes the SOAP headers of incoming requests that have been processed. If we set this property to 'true', Synapse preserves the SOAP headers. | ||
Example |
|
SERVER_IP
Name | SERVER_IP |
---|---|
Possible Values | IP address or hostname of the ESB host |
Default Behavior | Set automatically by the mediation engine upon startup |
Scope | synapse |
FORCE_ERROR_ON_SOAP_FAULT
Anchor | ||||
---|---|---|---|---|
|
Name | FORCE_ERROR_ON_SOAP_FAULT | ||
---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | true | ||
Scope | synapse(default) | ||
Description | When a SOAP error occurs in a response, the SOAPFault sent from the back end is received by the out sequence as a usual response by default. If this property is set to | ||
Example |
|