Scenario 3: Using an Xquery endpoint to filter messages

This scenario applies only to a Talend solution with ESB.

In this scenario, we will use a cMessagingEndpoint
component to call a Route Resource as an Xquery parser to extract messages from the
local file system.

The following sample XML file is used in this scenario:

&lt;people&gt;
  &lt;person id="8"&gt;
    &lt;firstName&gt;Ellen&lt;/firstName&gt;
    &lt;lastName&gt;Ripley&lt;/lastName&gt;
    &lt;city&gt;Washington&lt;/city&gt;
  &lt;/person&gt;  
  &lt;person id="9"&gt;
    &lt;firstName&gt;Peter&lt;/firstName&gt;
    &lt;lastName&gt;Green&lt;/lastName&gt;
    &lt;city&gt;London&lt;/city&gt;
  &lt;/person&gt;
&lt;/people&gt;

<firstName>Ellen</firstName>

<lastName>Ripley</lastName>

<city>Washington</city>

</person>

<firstName>Peter</firstName>

<lastName>Green</lastName>

<city>London</city>

</person>

</people>

Document get from Talend https://help.talend.com

Thank you for watching.

Docs 6.x

0 Comments

Inline Feedbacks

View all comments

Scenario 3: Using an Xquery endpoint to filter messages – Docs for ESB 6.x

Scenario 3: Using an Xquery endpoint to filter messages

My Website Links

Tags