perfsonar development work

[Jason Zurawski <>]

Ulisses;

> In any case please note that the Message being returned is printed just before 
> the return of the performAction method. All objects returned to the networksData 
> have been filled in a different scope (fillNodesNetworks()) to performAction. 
>
>   

So just so I am sure where you are coming from, you are able to do 
'XMLUtils.serializeXML(response)' in performAction and it works fine, 
but it does not work when printed in the RequestHandler?

There are two xml output methods, toXML (which just prints text 
representation of the objects) and getDOM (which the XMLUtils use to get 
a DOM Document).  You can try using these directly in each location and 
see if any errors are generated.

> IMHO If the XML is printed correctly the DOM should be converted afterwards. 
>
>   

I agree, I will examine the DOM code to be sure I haev not missed 
anything, but at this point I unsure what else could be the problem.

> I don't know where the XML -> DOM conversion is done, but the last point I could 
> print the Message "correctly" is Request.java:execute():
>
>   

getDOM (called on any object), which the XMLUtils uses.  Try calling it 
directly perhaps in different locations. 

> <nmwg:message id="msg2_resp" messageIdRef="msg2"
>     type="TOPSDownloadDBResponse" 
> xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";>
>     <nmwg:metadata id="TOPSDownloadDBResponseMetadata_0"/>
>     <nmwg:data id="TOPSDownloadDBResponse_0" 
> metadataIdRef="TOPSDownloadDBResponseMetadata_0">
>         <nmwg:metadata id="TOPSDownloadDBResponseMetadata_0"/>
>         <nmwg:data id="localhost.localdomain.-7edd1411:10cb415db62:-7ffe">
>             <nmwgtopo3:link
>                 id="localhost.localdomain.-7edd1411:10cb415db62:-7fff" 
> xmlns:nmwgtopo3="http://ggf.org/ns/nmwg/topology/l3/3.0/";>
>                 <nmwgtopo3:interface
>                     id="localhost.localdomain.-7edd1411:10cb415db62:-8000" 
> interfaceIdRef="private_index: 0, snmp_ifindex: unknown">
>                     
> <nmwgtopo3:ifDescription>GE-0/0/0.20</nmwgtopo3:ifDescription>
>                     <nmwgtopo3:type>other</nmwgtopo3:type>
>                     <nmwgtopo3:capacity>0</nmwgtopo3:capacity>
>                     <nmwgtopo3:netmask>62.40.98.40/29</nmwgtopo3:netmask>
>                     <nmwgtopo3:ipAddress value="62.40.98.41"/>
>                 </nmwgtopo3:interface>
>                 <nmwgtopo3:name>be1.be.geant.net_62.40.98.40/29 - 
> _</nmwgtopo3:name>
>             </nmwgtopo3:link>
>         </nmwg:data>
>     </nmwg:data>
> </nmwg:message>
>
> Does this proves that the Message and it's childs are correct both as object 
> hierarchy and as xml syntax?
>
>   

I will verify this with the schema tools, but it does look syntactically 
by sight.  I do wonder why you are nesting the metadata and data like 
that though:

<message>
 <metadata/>
 <data>
   <metadata/>
   <data>
   ...
   </data>
 </data>
</message>

Is this what you wanted?

-jason