SEEK

• Bug 2380 has been marked as a duplicate of this bug. ***

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.

adding a link to bug 2649

Original Bugzilla ID was 2650