perfsonar-user - Re: [perfsonar-user] Strange responses from http://loco4.man.poznan.pl:8090/axis/services/LookupService
Subject: perfSONAR User Q&A and Other Discussion
List archive
Re: [perfsonar-user] Strange responses from http://loco4.man.poznan.pl:8090/axis/services/LookupService
Chronological Thread
- From: Maciej Glowiak <>
- To: Vlada Macek <>
- Cc:
- Subject: Re: [perfsonar-user] Strange responses from http://loco4.man.poznan.pl:8090/axis/services/LookupService
- Date: Wed, 14 Feb 2007 15:33:49 +0100
- Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEUAAAD///+l2Z/dAAAA CXBIWXMAAEU1AABFNQF8gVf5AAAAB3RJTUUH1QYQDjo6uEWvwgAAAM5JREFUGNNN0LFqAkEUheGj KRZsfATrvENgYyH4APabxwgWGUUQC99BsNDCInUq7VImbbDZ0kayxBXMuN7jvTuKVh//mZlmQKZ1 EhQ8GAVgZECspEBdWQHRjR70KlgFKkoUaCw3ijSYQ4n5HfBK4a4jDcdDQPol/80Sr9BxZOOL4Fmr Jq8VBx7eopaSPvWGOm67fqol3j1q0XNs7Nk2cs6MU6gPNzf+ZGKQX4Ek8H6rAnFZnXB2vJxJcv8g C2P+WzL4tD+Txc4KydrIkh+eAdo01QbjQ84vAAAAAElFTkSuQmCC
- Organization: Poznan Supercomputing and Networking Center
Vlada Macek wrote:
Hi,
during the testing of the new LS client against
http://loco4.man.poznan.pl:8090/axis/services/LookupService, we've found
the responses deviate somehow from the specifications on
wiki.perfsonar.net. Can that mean the LS is old version? I think the
responses are vague. When the items below get corrected, the responses
will be better parsable:
1. Returned the result codes in the form 'result.success' instead of
'success.ls.register' for registration operation. Should I fix the
client to accept this answer for success? I consider it unclean
solution.
2. 'id' attribute in response's data and metadata get strange "_0"
suffix, for example 'resultCodeMetadata_0'. I think unified
'resultCodeMetadata' and 'resultCodeData' ids would be great for
parsing and I vote for them to be labeled required on the page
http://wiki.perfsonar.net/jra1-wiki/index.php/LS_Messages.
3. Response <nmwg:message> root element does not hold the required
'metadataIdRef' attribute referencing the 'id' of the request.
My client parses the registration response using this xpath expression,
which I consider good:
/nmwg:message[@type="LSRegisterResponse"
and
metadataIdRef="ls_client_request"]/nmwg:metadata[@id="resultCodeMetadata"]/nmwg:eventType
The items 2. and 3. above both keep the expression from finding the
correct <eventType> and item 1. means the string success.ls.register
cannot be successfully matched to indicate success.
Yes, the LS is quite an old version. I don't know exactly what version it is, but most of these things were reported as bugs and corrected. For sure 1) and 2). I don't remember if 3) as well, but I'll check it.
So probably loco4 LS is not a good choice. I think after releasing next perfSONAR suite we'll be installing the newest version. Until that time you should use 1.1RC2 just to avoid inconsistency between functionalities.
Maciej
--
--------------------------------------------------------------------
| Maciej Glowiak Network Research and Development ||
|
Poznan Supercomputing and Networking Center ||
| (+48 61) 858 2024 -- skype_id: maciej_psnc GG: 4526858 ||
====================================================================
- Strange responses from http://loco4.man.poznan.pl:8090/axis/services/LookupService, Vlada Macek, 02/14/2007
- Re: [perfsonar-user] Strange responses from http://loco4.man.poznan.pl:8090/axis/services/LookupService, Maciej Glowiak, 02/14/2007
Archive powered by MHonArc 2.6.16.