![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I need to extract the data from the following XML file (fragment) which consists of and order number (in this case 415045) and some related part numbers into a .NET dataset. The part number data is contained in other parts of the file which are referenced by links to named anchors eg I need to extract the 'id190' from this line of code: <ns1829687187:Part href="#id190"/>. |
|
multiRef id="id141" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns1829687187:FormatBOrder" ns1829687187 rderNum xsi:type="xsd:string">415045</ns1829687187 rderNumns1829687187:buildDate xsi:type="xsd:dateTime">2007-07-10T23:00:00.000Z</ns1829687187:buildDate ns1829687187:buildSeq xsi:type="xsd:long">515</ns1829687187:buildSeq |
#3
| |||
| |||
|
|
I need to extract the data from the following XML file (fragment) which consists of and order number (in this case 415045) and some related part numbers into a .NET dataset. The part number data is contained in other parts of the file which are referenced by links to named anchors eg I need to extract the 'id190' from this line of code: <ns1829687187:Part href="#id190"/>. |
|
multiRef id="id141" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns1829687187:FormatBOrder" ns1829687187 rderNum xsi:type="xsd:string">415045</ns1829687187 rderNumns1829687187:buildDate xsi:type="xsd:dateTime">2007-07-10T23:00:00.000Z</ns1829687187:buildDate ns1829687187:buildSeq xsi:type="xsd:long">515</ns1829687187:buildSeq |
#4
| |||
| |||
|
|
That fragment is not well-formed XML with namespaces as several prefixes (soapenc, soapenv, xsi, ns1829687187) are not bound to a namespace URI. So we need to see the namespace declarations if you need help processing that XML. -- Martin Honnen --- MVP XML http://JavaScript.FAQTs.com/ |
rderNum xsi:type="xsd:string">097294</ns1829687187
rderNum>
fflineDate xsi:type="xsd:dateTime" xsi:nil="true"/>
refix xsi:type="xsd:string">XH42</ns1829687187
refix>
artDesc xsi:type="xsd:string">SHLD VEH IDENT
artDesc>
#5
| |||
| |||
|
|
That fragment is not well-formed XML with namespaces as several prefixes (soapenc, soapenv, xsi, ns1829687187) are not bound to a namespace URI. So we need to see the namespace declarations if you need help processing that XML. -- Martin Honnen --- MVP XML http://JavaScript.FAQTs.com/ |
rderNum xsi:type="xsd:string">097294</ns1829687187
rderNum>
fflineDate xsi:type="xsd:dateTime" xsi:nil="true"/>
refix xsi:type="xsd:string">XH42</ns1829687187
refix>
artDesc xsi:type="xsd:string">SHLD VEH IDENT
artDesc>
#6
| |||
| |||
|
|
"Martin Honnen" wrote: That fragment is not well-formed XML with namespaces as several prefixes (soapenc, soapenv, xsi, ns1829687187) are not bound to a namespace URI. So we need to see the namespace declarations if you need help processing that XML. Here is a truncated version of the whole file: soapenv:Envelope |
#7
| |||
| |||
|
|
"Martin Honnen" wrote: That fragment is not well-formed XML with namespaces as several prefixes (soapenc, soapenv, xsi, ns1829687187) are not bound to a namespace URI. So we need to see the namespace declarations if you need help processing that XML. Here is a truncated version of the whole file: soapenv:Envelope |
#8
| |||
| |||
|
|
Jonathan Attree wrote: "Martin Honnen" wrote: That fragment is not well-formed XML with namespaces as several prefixes (soapenc, soapenv, xsi, ns1829687187) are not bound to a namespace URI. So we need to see the namespace declarations if you need help processing that XML. Here is a truncated version of the whole file: soapenv:Envelope That is not well-formed either, it needs namespace declarations e.g soapenv:Envelope xmlns:soapenv="someURI" -- Martin Honnen --- MVP XML http://JavaScript.FAQTs.com/ |
#9
| |||
| |||
|
|
Jonathan Attree wrote: "Martin Honnen" wrote: That fragment is not well-formed XML with namespaces as several prefixes (soapenc, soapenv, xsi, ns1829687187) are not bound to a namespace URI. So we need to see the namespace declarations if you need help processing that XML. Here is a truncated version of the whole file: soapenv:Envelope That is not well-formed either, it needs namespace declarations e.g soapenv:Envelope xmlns:soapenv="someURI" -- Martin Honnen --- MVP XML http://JavaScript.FAQTs.com/ |
#10
| |||
| |||
|
|
These are the declarations at the top of the file: ?xml version="1.0" encoding="UTF-8"? soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" getOrdersForDateRangeResponse xmlns="http://obom/service/FormatB"><FilteredOrders href="#id0" xmlns=""/></getOrdersForDateRangeResponse multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns1829687187:FormatBFilter" xmlns:ns1829687187="http://obom/service/types" xmlns="" ns1829687187:filterId xsi:type="xsd:int">94</ns1829687187:filterId ns1829687187:Orders |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |