...
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
Name | transportNonBlockingClientApiNonBlocking | ||
---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | true | ||
Scope | axis2 | ||
Description | By default, Axis2 will spawn a new thread to handle each outgoing message. To change this behavior, remove this property from the message. Removal of this property could be vital when queuing transports like JMS are involved. | ||
Example |
|
...
transportNonBlocking
Name | ClientApiNonBlocking transportNonBlocking | ||
---|---|---|---|
Possible Values | "true", "false" | ||
Default Behavior | true | ||
Scope | axis2 | ||
Description | By default, Axis2 will spawn a new thread to handle each outgoing message. To change this behavior, remove this property from the message. Removal of this property could be vital when queuing transports like JMS are involvedThis 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 |
|
...