perfsonar-dev - Re: [pS-dev] LS XQuery problem
Subject: perfsonar development work
List archive
- From: Maciej Glowiak <>
- To: Yee-Ting Li <>
- Cc:
- Subject: Re: [pS-dev] LS XQuery problem
- Date: Wed, 28 Mar 2007 09:33:46 +0200
Hi Yee,
Yee-Ting Li napisaĆ(a):
i' ve been playing around with the lookup service for some automated analysis.Yes, that's normal behaviour. In fact, the responce for XQuery may be any XML (or even not valid XML, just a string without root element), so we decided to encode XML. Of course in most of cases the content will be NMWG but we cannot guarantee it.
i have a few problems i was hoping someone could shed some light on:
1) when i query the LS, it appears that all data within the response's <psservice:datum/> elements are returned as a string (ie. the < and > become < and >); is this normal?
2) with registered netutil metadata (showing the interface's metadata), the supplied entries do not appear to be namespaced correctly; nmwgt is not defined as a namespace within the service.
Services register by themselves, so perhaps the mistake is in the registration message. LS stores everything what was sent to be registered.
3) queries where i try to use the standard '{}' and element definitions to format the output of the query do not appear to work with an error 'xmltypelsserviceengine: no eventType in metadata (type of query) error.
You must use <eventType>...</enventType> inside subjests. Now I don't have the details for that, but you may see the example of query request (LSLookupRequest) on the SVN (or the tarball release) in schema/example-instances/.../LS/test
(sorry for not providing you all the details but I am on the meeting and have just configured network) :)
If it doesn't help, let me know, I'll provide more details.
Best regards
Maciej
- LS XQuery problem, Yee-Ting Li, 03/27/2007
- Re: [pS-dev] LS XQuery problem, Maciej Glowiak, 03/28/2007
- Re: [pS-dev] LS XQuery problem, Yee-Ting Li, 03/30/2007
- Re: [pS-dev] LS XQuery problem, Maciej Glowiak, 03/28/2007
Archive powered by MHonArc 2.6.16.