Page Comparison

...

Property: synapse.isresponse

Name

synapse.isresponse

Possible Values

"true", "false"

Default Behavior

none

Scope

axis2

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

Code Block
<property name="synapse.isresponse" value="true" scope="axis2"/>

Property: 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 "true" on a message, the ESB will forward it without altering its existing WS-Addressing headers.

Example

Code Block
<property name="PRESERVE_WS_ADDRESSING" value="true"/>

Property: RESPONSE

Name

RESPONSE

Possible Values

"true", "false"

Default Behavior

none

Scope

synapse

Description

The same as synapse.isresponse property. It is recommended to use this property to flag messages as responses instead of the synapse.isresponse property.

Example

Code Block
<property name="RESPONSE" value="true"/>

Property: 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

Code Block
<property name="OUT_ONLY" value="true"/>

Property: 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

Code Block
<property name="ERROR_CODE" value="100100"/>

Property: 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

Code Block
<log level="custom"> <property name="Cause" expression="get-property('ERROR_MESSAGE')"/> </log>

Property: 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

Code Block
<log level="custom"> <property name="Trace" expression="get-property('ERROR_DETAIL')"/> </log>

Property: 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.

Property: 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

Code Block
<property name="TRANSPORT_HEADERS" action="remove" scope="axis2"/>

Property: 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, for example, text/xml, application/xml.

Example

Code Block
<property name="messageType" value="text/xml" scope="axis2"/>

Property: ContentType

Name

ContentType

Possible Values

string

Default Behavior

Value of the Content-type header of the incoming request.

Scope

axis2

Description

Message builder is selected based on this property. This property should specify the content type.

Example

Code Block
<property name="ContentType" value="text/xml" scope="axis2"/>

Property: 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

Code Block
<property name="disableAddressingForOutMessages" value="true" scope="axis2"/>

Property: transportNonBlocking

Name

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 involved.

Example

Code Block
<property name="transportNonBlocking" action="remove" scope="axis2" value="true"/>

Property: ClientApiNonBlocking

Name	ClientApiNonBlocking
Possible Values	"true", "false"
Default Behavior	true
Scope	axis2
Description	By default, Axis2

will spawn

spawns a new thread to handle each outgoing message

. To change this behavior,

. This property holds the primary thread until a VFS proxy writes to a VFS endpoint. You need to remove this property from the message

. Removal of this property could be vital when

to change this behavior when queuing transports like JMS are involved.

Example

Code Block
<property name="ClientApiNonBlocking" action="remove" scope="axis2"/>

Property: endpoint.operation

Name

endpoint.operation

Possible Values

string

Default Behavior

none

Scope

synapse

Description

If this property is set, endpoint statistics will be calculated for the specified operation.

Example

Code Block
<property name="endpoint.operation" scope="axis2" value="OperationName"/>

Property: 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

Code Block
<log level="custom"> <property name="INCOMING_TRANSPORT" expression="get-property('TRANSPORT_IN_NAME')"/> </log>

Property: preserveProcessedHeaders

Name

preserveProcessedHeaders

Possible Values

"true", "false"

Default Behavior

Preserving SOAP headers

Scope

synapse(default)

Description

If we set this property to 'true', synapse tries to preserve the SOAP header of incoming requests. Else, by default synapse removes the soap headers.

Example

Code Block
<property name="preserveProcessedHeaders" value="true" scope="default"/>

Property: 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

Versions Compared

Old Version 6

New Version Current

Key

Property: synapse.isresponse

Property: PRESERVE_WS_ADDRESSING

Property: RESPONSE

Property: OUT_ONLY

Property: ERROR_CODE

Property: ERROR_MESSAGE

Property: ERROR_DETAIL

Property: ERROR_EXCEPTION

Property: TRANSPORT_HEADERS

Property: messageType

Property: ContentType

Property: disableAddressingForOutMessages

Property: transportNonBlocking

Property: ClientApiNonBlocking

Property: endpoint.operation

Property: TRANSPORT_IN_NAME

Property: preserveProcessedHeaders

Property: SERVER_IP