[seek-dev] [Bug 2650] - ecogrid returnfields need to support more xpath

[bugzilla-daemon@ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=2650


berkley at nceas.ucsb.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |blocker




------- Comment #2 from berkley at nceas.ucsb.edu  2006-11-11 10:03 -------
this turns out to be a bigger issue than i thought.  in face, i think it's a
blocker for getting the remote actor search working in kepler.  I had thought
that, at least, the ecogrid would always return the returnfields in the same
order which was allowing me to hack this by doing two returnfield queries then
parsing the results (which were in effect name/value pairs).  In fact, when i
tried this on my laptop, the results were all hosed because the ecogrid
returned the returnfields in totally different order than on my desktop.  This
has to be fixed soon.

Here's an example of the returnfields on my desktop with the query
<returnfield>//property/@name</returnfield>
<returnfield>//property/@value</returnfield>

returnfield: f1:karId
returnfield: f0:urn:lsid:kepler-project.org:kar:3:1
returnfield: f1:semanticType111
returnfield: f0:urn:lsid:localhost:onto:1:1#TextualOutputActor

Note the values intuitively alternate.  This makes sense to me.  However, this
is what I get when I do the same query on my laptop:

returnfield: f1:karId
returnfield: f1:semanticType111
returnfield: f0:urn:lsid:kepler-project.org:kar:3:1
returnfield: f0:urn:lsid:localhost:onto:1:1#TextualOutputActor

this is totally unparsable.