Step 3: Nested data formats

We will now fetch the project list again, but this time request an ATOM representation. To this end we reset the GET resource node.
Keep in mind that resetting a node will not revert requests you have sent! This is especially important for requests that modify data on the server.

Now open the dialog, switch to the Header Setting tab and select application/atom+xml in the drop-down menu next to the Accept textfield. Press Add and then OK. This will add an accept field with the value application/atom+xml to your request.

Adding an Accept header

Execute the node and re-run the Read REST representation node in with Autodetection as Data Format. This time you should obtain a different data table as output. It contains more columns and its column names are different. The reason for this is that the representation the server has sent contains more information.

Converted ATOM representation

Have a look on the view of the GET resource node.

ATOM representation

The Read REST representation node has already filtered out some of the information (like the title and the content-type tags or the rel attributes of the link elements). It is possible to change the filtering by adjusting the options Ignore tags called and Ignore attributes called in the dialog of the reader node. This would require to set the Data Format to ATOM (Simple ASF).

Note furthermore that the column names are dotted. This reflects the hierarchy of the ATOM elements. Take the element ps:customer, for instance. Its values are presented by the columns project.customer.id, and project.customer.link.href.

LinkedInTwitterShare