Page Comparison

...

...

Syntax

...

• Clone- By setting the clone configuration, the message can be cloned or used as a reference during enriching. The default value is falsetrue.
  • True
  • False
• Type- The type that the mediator uses from the original message to enrich the modified message that passes through the mediator.
  • Custom - Custom XPath value.
  • Envelope - Envelope of the original message used for enriching.
  • Body - Body of the original message used for enriching.
  • Property - Specifies a property.
  • Inline - Specifies an inline XML value.
• XPath Expression

...

Example 1: Setting the property symbol

In this example, we are setting the property symbol. Later, you can log it using the Log Mediator.

<enrich xmlns="http://ws.apache.org/ns/synapse">
           <source clone="false" type="envelope" xpath="" property="" />
           <target action="replace" type="body" xpath="" property="" />
 </enrich>

...

Example 2: Adding a child object to a property

...

...

In this example, we add a child property named Lamborghini to a property named Cars. The configuration for this is as follows:

Code Block
language html/xml
<proxy xmlns="http://ws.apache.org/ns/synapse" name="_TestEnrich" transports="https,http" statistics="disable" trace="enable" startOnLoad="true"> <target> <inSequence> <enrich> <source type="inline" clone="true"> <Cars/> </source> <target type="property" property="Cars"/> </enrich> <log level="custom"> <property name="PekeCarListBeforeEnrich" expression="get-property('Cars')"/> </log> <enrich> <source type="inline" clone="true"> <Car>Lamborghini</Car> </source> <target action="child" xpath="$ctx:Cars"/> </enrich> <log level="custom"> <property name="PekeCarListAfterEnrich" expression="get-property('Cars')"/> </log> </inSequence> <outSequence/> </target> <description></description> </proxy>

...

The child property can also be added using the design view

...

 

Excerpt
hidden true
Example 2 is written with reference to /wiki/spaces/FAQ/pages/37781537.

...

as shown below.
 

1. Add the Enrich mediator as a child to the required sequence as shown below.
   
   Image Added
   
   
2. Configure the Enrich Mediator as shown below.
   
   Image Added

Excerpt
hidden true
Example 2 is written with reference to /wiki/spaces/FAQ/pages/37781537.

Example 3 - Adding a SOAPEnvelope type object as a property to a message

In this example, we add the SOAP envelope in a SOAP request as a property to a message. The Enrich mediator is useful in this scenario since adding the property directly using the Property mediator results in the SOAPEnvelope object being created as an OM type object. The OM type object created cannot be converted back to a SOAPEnvelope object.

Code Block
language xml
<enrich> <source type="envelope" clone="true"/> <target type="property" property="ExtractedEnvelope"/> </enrich>

Excerpt
hidden true
Added this content for the FAQ When ExtractedEnvelope is a SOAPEnvelope with OM type, why do we get "EnrichMediator SOAPEnvelope is expected" for SOAP requests?

 

Example 4 - Preserving the original payload

 

In this example, you copy the original payload to a property using the Enrich mediator.

 

Code Block
language xml
<enrich> <source clone="false" type="body"/> <target action="replace" type="property" property="ORGINAL_PAYLOAD"/> </enrich>

 

Then whenever you need the original payload, you replace the message body with this property value using the Enrich mediator as follows:

 

Code Block
language xml
<enrich> <source clone="false" type="property" property="ORIGINAL_PAYLOAD"/> <target action="replace" type="body"/> </enrich>

 

For other example using the Enrich mediator, see Sample 15: Using the Enrich Mediator for Message Copying and Content Enrichment and Sample 440: Converting JSON to XML Using XSLT.

Excerpt
hidden true
Description of the Enrich Mediator in WSO2 ESB.