Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] failure of converting returning message (XML) to DOM

Subject: perfsonar development work

List archive

Re: [pS-dev] failure of converting returning message (XML) to DOM


Chronological Thread 
  • From: ulisses <>
  • To: Roman Lapacz <>
  • Cc: ,
  • Subject: Re: [pS-dev] failure of converting returning message (XML) to DOM
  • Date: Thu, 24 Aug 2006 12:12:20 +0200


Hi Roman!

On 2006-08-23 13:27:28, Roman Lapacz wrote:
> ulisses wrote:
> >Hi again
> >
> >I managed to have a very minimum version of the XML document that fails
> >to convert to DOM:
> >
> ><nmwg:message id="localhost.localdomain.66dffd41:10d3ab5e77b:-7ffe"
> > type="TOPSDownloadDBResponse"
> > xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";>
> > <nmwg:metadata id="TOPSDownloadDBResponseMetadata"/>
> > <nmwg:data id="TOPSDownloadDBResponse"
> > metadataIdRef="TOPSDownloadDBResponseMetadata">
> > <nmwg:data id="localhost.localdomain.66dffd41:10d3ab5e77b:-7fff">
> >
>
> data inside data looks strange and I don't think it's correct

so, should I instead do something like removing a <data
id="TOPSDownloadDBResponseMetadata"> section
and do instead:

<nmwg:metadata id="TOPSDownloadDBResponseMetadata"/>
<nmwg:data id="localhost.localdomain.-240dae5e:10d3f9071a8:-6197">
<nmwgtopo3:link
id="localhost.localdomain.-240dae5e:10d3f9071a8:-7fe5"
xmlns:nmwgtopo3="http://ggf.org/ns/nmwg/topology/l3/3.0/";>
<nmwgtopo3:interface
id="localhost.localdomain.-240dae5e:10d3f9071a8:-7fe6"
interfaceIdRef="20290">
<nmwgtopo3:ifDescription>LO0</nmwgtopo3:ifDescription>
<nmwgtopo3:type>other</nmwgtopo3:type>
<nmwgtopo3:capacity>0</nmwgtopo3:capacity>
<nmwgtopo3:netmask>62.40.102.46/32</nmwgtopo3:netmask>
<nmwgtopo3:ipAddress value="62.40.102.46"/>
</nmwgtopo3:interface>
<nmwgtopo3:name>ie1.ie.geant.net_62.40.102.46/32 -
_</nmwgtopo3:name>
</nmwgtopo3:link>
</nmwg:data>
<nmwg:data id="localhost.localdomain.-240dae5e:10d3f9071a8:-6196">
<nmwgtopo3:node
id="localhost.localdomain.-240dae5e:10d3f9071a8:-6242"
xmlns:nmwgtopo3="http://ggf.org/ns/nmwg/topology/base/3.0/";>
<nmwgtopo3:interface
id="localhost.localdomain.-240dae5e:10d3f9071a8:-6243"
interfaceIdRef="59513"/>
<nmwgtopo3:interface
id="localhost.localdomain.-240dae5e:10d3f9071a8:-6245"
interfaceIdRef="59253"/>
<nmwgtopo3:interface
id="localhost.localdomain.-240dae5e:10d3f9071a8:-6246"
interfaceIdRef="59249"/>
<nmwgtopo3:interface
id="localhost.localdomain.-240dae5e:10d3f9071a8:-6244"
interfaceIdRef="59385"/>
<nmwgtopo3:hostName>swiBAS1.switch.ch</nmwgtopo3:hostName>
<nmwgtopo3:name>swiBAS1.switch.ch</nmwgtopo3:name>
</nmwgtopo3:node>
<nmwgtopo3:node
id="localhost.localdomain.-240dae5e:10d3f9071a8:-6318"
xmlns:nmwgtopo3="http://ggf.org/ns/nmwg/topology/base/3.0/";>
<nmwgtopo3:interface
id="localhost.localdomain.-240dae5e:10d3f9071a8:-631b"
interfaceIdRef="59646"/>
<nmwgtopo3:interface
id="localhost.localdomain.-240dae5e:10d3f9071a8:-631c"
interfaceIdRef="59517"/>
<nmwgtopo3:interface
id="localhost.localdomain.-240dae5e:10d3f9071a8:-6319"
interfaceIdRef="59686"/>
<nmwgtopo3:interface
id="localhost.localdomain.-240dae5e:10d3f9071a8:-631a"
interfaceIdRef="59671"/>
<nmwgtopo3:interface
id="localhost.localdomain.-240dae5e:10d3f9071a8:-631d"
interfaceIdRef="59167"/>
<nmwgtopo3:hostName>swiFF2.switch.ch</nmwgtopo3:hostName>
<nmwgtopo3:name>swiFF2.switch.ch</nmwgtopo3:name>
</nmwgtopo3:node>
</nmwg:data>
</nmwg:message>

>
> > <nmwgtopo3:link
> > id="localhost.localdomain.66dffd41:10d3ab5e77b:-8000"
> > xmlns:nmwgtopo3="http://ggf.org/ns/nmwg/topology/l3/3.0/";>
> >
>
> what's the difference between your namespace and this
> xmlns:nmwgtopo3="http://ggf.org/ns/nmwg/topology/base/3.0/"; ?

in this case, for me the most important is that topology/l3/ has fields
specific to layer 3

Thanks so much

Ulisses



Archive powered by MHonArc 2.6.16.

Top of Page