Skip to Content
0
Former Member
Jun 16, 2016 at 04:02 PM

HCI Integration - Content Filter and XPath problem

3557 Views

Hi everyone,

I have a little question. On my integration project I'm trying to filter the informations of the incoming payload. For this I'm using a Filter with an XPath expression that match my needs (I'm trying to get a full node). After the Filter, the Content Modifier serve me to insert the node coming from the Filter in a well formed XML style :

<?xml version="1.0" encoding="UTF-8"?>

<SALESORDER_CREATEFROMDAT202>

${in.body}

</SALESORDER_CREATEFROMDAT202>

The ECC send back an error (SRT_CORE/131), but I managed to understand why without solving it.

The problem is the XPath expression or the way XPath is interpreted by HCI.

Let me explain my point : if your XPath is //foo/text(), the result is the textual value of a foo element. If you write //foo or //foo/node() you get a foo element.

Here is my problem with the behavior of XPath in HCI, I tried to get a node, and with ${in.body} insert it in the XML of the Content Modifier. When checking in transaction SRTUTIL, it just concatenate all textual value of my payload, discarding all the tags.

Do anyone know if it's standard behavior, or not ?

Best regards,

Julen.

Attachments