Better Support of XML-Data-Sources
Hi, when creating an XML-DataSource I sometimes met a problem regarding the parameter "Column XPaths". Using the select-Button, I choose the xml-node to use for "Column XPaths". But I always get a...
Forum Discussion
Hi Rao,
the wildcard (*) is matching all namespace prefixes, isn't it.
So if using it, one cannot ensure, that the correct/required namespace prefix is used.
e.g.
*:name is matching ns2:name and ns3:name
Maybe this could be ensured by checking the schema compliance of the corresponding soap response. But this is nothing but a workaround.
Anyway, if there are two nodes of the same name, which can be distinguished only by their namespace, this workaround isn't helpfull anymore.
The followong example shows, what I mean. There a two name-nodes. One contains the original spelling (inlcuding mutated vowels/umlauts), the other one
To be true, this migth be a rare scenario. But you know Murphy's law, don't you?
Best regards
the wildcard (*) is matching all namespace prefixes, isn't it.
So if using it, one cannot ensure, that the correct/required namespace prefix is used.
e.g.
*:name is matching ns2:name and ns3:name
Maybe this could be ensured by checking the schema compliance of the corresponding soap response. But this is nothing but a workaround.
Anyway, if there are two nodes of the same name, which can be distinguished only by their namespace, this workaround isn't helpfull anymore.
The followong example shows, what I mean. There a two name-nodes. One contains the original spelling (inlcuding mutated vowels/umlauts), the other one
<ns1:person>
<ns2:name>Dömme</ns2:name>
<ns3:name>Doemme</ns3:name>
</ns1:person>
To be true, this migth be a rare scenario. But you know Murphy's law, don't you?
Best regards