In addition to standard XPath functions, the ESB supports the following custom functions for working with XPath expressions:
base64Encode() function
The base64Encode function returns the base64-encoded value of the specified string.
Syntax:base64Encode(string)
Next, refer Synapse XPath Variables.
synapse:get-property()
The get-property() function allows any XPath expression used in a configuration to look up information from the current message context. Using the Property mediator, you can retrieve properties from the message context and header.
The syntax of the function takes the following format.
get-property(String propertyName)get-property(String scope, String propertyName)
The function accepts scope as an optional parameter. It retrieves a message property at the given scope, which can be one of the following.
If you provide only the property name without the scope, the default Synapse scope will be used.
Synapse Scope
When the scope of a property mediator is Synapse, its value is available throughout both the in sequence and the out sequence. Message context properties within the Synapse scope can be retrieved from the default scope. In addition to the user-defined properties, you can retrieve the following special properties from the default scope.
| Name | Return Value |
| To | Incoming URL as a String, or empty string («») if a To address is not defined. |
| From | From address as a String, or empty string («») if a From address is not defined. |
| Action | SOAP Addressing Action header value as a String, or empty string («») if an Action is not defined. |
| FaultTo | SOAP FaultTo header value as a String, or empty string («») if a FaultTo address is not defined. |
| ReplyTo | ReplyTo header value as a String, or empty string («») if a ReplyTo address is not defined. |
| MessageID | A unique identifier (UUID) for the message as a String, or empty string («») if a MessageID is not defined. This ID is guaranteed to be unique. |
| FAULT | TRUE if the message has a fault, or empty string if the message does not have a fault. |
| MESSAGE_FORMAT | Returns pox, get, soap11, or soap12 depending on the message. If a message type is unknown this returns soap12 |
| OperationName | Operation name corresponding to the message. A proxy service with a WSDL can have different operations. If the WSDL is not defined, ESB defines fixed operations. |
To access a property with the Default scope inside the mediate() method of a mediator, you can include the following configuration in a custom mediator created using the Class Mediator:
public boolean mediate(org.apache.synapse.MessageContext mc) {
// Available in both in-sequence and out-sequenc
String propValue = (String) mc.getProperty("PropName");
System.out.println("SCOPE_SYNAPSE : " + propValue);
return true;
}
Axis2 scope
When the scope of a property mediator is Axis2, its value is available only throughout the sequence for which the property is defined (e.g. if you add the property to an in sequence, its value will be available only throughout the in sequence). You can retrieve message context properties within the Axis2 scope using the following syntax.
Syntax:get-property('axis2', String propertyName)
To access a property with the Axis2 scope inside the mediate() method of a mediator, you can include the following configuration in a custom mediator created using the Class Mediator:
public boolean mediate(org.apache.synapse.MessageContext mc) {
org.apache.axis2.context.MessageContext axis2MsgContext;
axis2MsgContext = ((Axis2MessageContext) mc).getAxis2MessageContext();
// Available only in the sequence the property is defined.
String propValue = (String) axis2MsgContext.getProperty("PropName");
System.out.println("SCOPE_AXIS2 : " + propValue);
return true;
}
axis2-client
This is similar to the Synapse scope. The difference is that it can be accessed inside the mediate() method of a mediator by including one of the following configurations in a custom mediator, created using the Class Mediator:
public boolean mediate(org.apache.synapse.MessageContext mc) {
org.apache.axis2.context.MessageContext axis2MsgContext;
axis2MsgContext = ((Axis2MessageContext) mc).getAxis2MessageContext();
String propValue = (String) axis2MsgContext.getProperty("PropName");
System.out.println("SCOPE_AXIS2_CLIENT - 1 : " + propValue);
or
propValue = (String) axis2MsgContext.getOptions().getProperty("PropName");
System.out.println("SCOPE_AXIS2_CLIENT - 2: " + propValue);
return true;
}
Transport scope
When the scope of a property mediator is Transport, it will be added to the transport header of the outgoing message from the ESB. You can retrieve message context properties within the transport scope using the following syntax.
Syntax:get-property('transport', String propertyName)
Registry scope
You can retrieve properties within the registry using the following syntax.
Syntax:get-property('registry', String registryPath@propertyName)get-property('registry', String registryPath)
System scope
You can retrieve Java System properties using the following syntax.
Syntax:get-property('system', String propertyName)
Note: system scope is only available in WSO2 ESB 4.8.0 or later versions
Operation scope
You can retrieve a property in the operation context level from the operation scope. Operation scope is used to preserve properties within iterated/cloned message flows.
Syntax:get-property('operation', String propertyName)