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: Loukik Kudarimoti <>
  • To: ulisses <>
  • Cc: ,
  • Subject: Re: [pS-dev] failure of converting returning message (XML) to DOM
  • Date: Fri, 25 Aug 2006 15:49:33 +0100

Hi Ulisses.

ulisses wrote:
Hi Loukik!

first of all, thanks so much for your reply
That is alright :) don't mention it.


<snip>
* Have you defined all possible message sequences for your service?
it is an stateless service for now, do you refer to this?
No. I meant to ask what are the possible types of requests and responses that your Topology service will be able to handle? Have you discussed these requests and responses with Jason and Martin?

no

<snip>
I mean to ask whether the requests and responses that you have discussed and agreed to use are the same as the ones your service is generating.

nobody never told me that I had to conform to other than the *.rnc files

I supossed I was the one to define the document, and that I only had to conform to this .rnc files.
I think Jeff has answered it perfectly. It is also my understanding that .rnc files only define the syntax. It can be base your messages on just them. Jason and Martin know the semantics. Hence at least for complex message types, its best to ask them both for their opinion.

Have you had any discussions with Martin and/or Jason about these messages at any point in the past?

Regards,
Loukik.

PS: To be honest, one data element inside another baffled me (it still does a little). For me, explaining that concept to somebody would be quite difficult.

Finally, if all above are ok, what is the error message being produced (look at catalina.out if you are testing it on a deployed service)
I think that I already asked you previously if it was possible force the XML to DOM parser to tell in which line it is the error?

The output is just:

<?xml version="1.0" encoding="UTF-8"?>
<nmwg:message xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"; id="resultCodeMessage">
<nmwg:metadata id="resultCodeMetadata">
<nmwg:eventType>error.common.parse_error</nmwg:eventType>
</nmwg:metadata>
<nmwg:data id="resultDescriptionData_for_resultCodeMetadata" metadataIdRef="resultCodeMetadata">
<nmwg:datum value="Cannot convert Message to DOM" />
</nmwg:data>
</nmwg:message>

I don't see any XML/DOM errors in the tomcat logs
Ok, if no logs are being generated to explain the error, I would suggest to add an entry in bugzilla asking for this feature. Can you do this?

yes, I will do in a moment

Thanks & have a nice weekend

regards

Ulisses




Archive powered by MHonArc 2.6.16.

Top of Page