XML XPath Filter - DevTest Solutions - 10.3 - CA Technologies Documentation
The lisa.xml.xpath.computeXPath.alwaysUseLocalName property controls whether the XPath local-name() function is always used during the XPath generation. The default value is false, which means that the local-name() function is used only when necessary. To generate an XPath that works regardless of an XML node namespace, set the value to true.
Can any one help me on where do we set lisa.xml.xpath.computeXPath.alwaysUseLocalName property to "true" so that this can function properly.
Add lisa.xml.xpath.computeXPath.alwaysUseLocalName=true to your local.properties file and restart the workstation or VSE or Simulator as required.
I would expect not, as this property is related to using namespaces or not.
Can you post an example of an XML (with non-English characters) and the xpath query on it that would fail?
Indeed, it looks like the Norwegian å-character already gets invalidated in the listener step (base listener step without any data protocols). I think you need to open a Broadcom support ticket to get this investigated.
Case #: 20251631
Musthaq Mohammed | TDM Test Analyst | IT BP – Release Train Management
DNB Bank ASA
Mob: +47 46355270
E-post: firstname.lastname@example.org| www.dnb.no
That would be good if you could like into this and share with us the reason of this behavior? Because it really confuses me, and I have worked with virtual services with Turkish characters and with Swedish characters, and I cannot recall ever running into this.
I was dabbling around myself. I took the data type of the payload out of the equation and was just sending in some text, in this case the primary Norwegian characters, here with a blank line first, second line 5 characters separated by a blank, and terminated by a newline:
å æ Æ ø Ø
As transaction body this results in:
And as you grab the body as a byte array, then you notice that the binary body payload is not placed as-is in the request object but that it has been processed. Each Norwegian character is replaced with this same byte-sequence: -17, -65, -67 (10 = newline; 32 is blank)
Sure Sankar, take your time..
I am working in Central European Time (UTC+1) and mostly available at our afternoon.
I am in office now