4595 2006-07-14 11:24 wsrf-query with a bad XPath query returns "null" 2006-07-17 15:36:46 1 1 1 Unclassified Java WS Core globus_wsrf_core 4.0.2 Macintosh All RESOLVED FIXED P3 normal --- 1 bacon@mcs.anl.gov gawor@mcs.anl.gov jwscore-dev@globus.org bacon@mcs.anl.gov 2006-07-14 11:24:14 ip-156:~/pkgs/globus-4.0.2 bacon$ bin/wsrf-query -s http://192.167.1.7:8888/wsrf/services/DefaultIndexService Foobar null This is the same result as if there were no results returned: ip-156:~/pkgs/globus-4.0.2 bacon$ bin/wsrf-query -s http://192.167.1.7:8888/wsrf/services/DefaultIndexService '/Foobar' null I would suggest that the first should generate some kind of "Invalid XPath expression: Foobar" error, and the second should return something like "No results found for XPath expression '/Foobar'". We saw the "null" result in a tutorial today, and it didn't help the student understand what had gone wrong. gawor@mcs.anl.gov 2006-07-14 16:25:28 Both expressions are valid. I will, however, update the client to display a nice error message if no results were returned. gawor@mcs.anl.gov 2006-07-14 16:52:08 Committed a fix to trunk to display a nice error msg when no results are returned: $ wsrf-query.bat -s http://192.168.1.102:8080/wsrf/services/ContainerRegistryService foo Query did not return any results. gawor@mcs.anl.gov 2006-07-17 15:36:46 Committed that fix to globus_4_0_branch too.