perfsonar-dev - Re: [pS-dev] failure of converting returning message (XML) to DOM
Subject: perfsonar development work
List archive
- From: ulisses <>
- To: Jason Zurawski <>
- Cc: ,
- Subject: Re: [pS-dev] failure of converting returning message (XML) to DOM
- Date: Fri, 28 Jul 2006 09:48:09 +0200
Hi again Jason!
On 2006-07-27 08:51:56, Jason Zurawski wrote:
> Ulisses;
>
[...]
>
> I will look into the DOM generation methods to see if there are any
> problems, but have you tried the suggestions I sent to you on Tuesday
> (July 25th)?
I think you refer to this
>> I am not able to get the code to compile, I am sure I am missing some
>> key libraries but that is really not important. The only real
>> suggestion I have is that in 'fillNodes()' you are dealing with the same
>> object in the same scope throughout the method. In
>> 'fillNodesNetworks()' (and subsequent function calls) you pass objects
>> into different scopes. This may or may not affect your ability to add
>> them as XML children.
I understand that Java always passes objects as references, so that should
not be the problem.
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.
IMHO If the XML is printed correctly the DOM should be converted afterwards.
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():
<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 wanted to attach a remote debugger using eclipse and java beans, but I have
not been able to do it.
regards
Ulisses
- failure of converting returning message (XML) to DOM, ulisses, 07/27/2006
- Re: [pS-dev] failure of converting returning message (XML) to DOM, Jason Zurawski, 07/27/2006
- Re: [pS-dev] failure of converting returning message (XML) to DOM, ulisses, 07/28/2006
- Re: [pS-dev] failure of converting returning message (XML) to DOM, Jason Zurawski, 07/28/2006
- Re: [pS-dev] failure of converting returning message (XML) to DOM, ulisses, 07/28/2006
- Re: [pS-dev] failure of converting returning message (XML) to DOM, Jason Zurawski, 07/27/2006
Archive powered by MHonArc 2.6.16.