Thank you for the speedy reply, my additional comments/questions inline
Michael Beddow wrote:
> Bill Beck wrote:
>> <exist:collection name="/db/dja" owner="admin" group="dba"
>> <exist:resource name="DJA01.xml" created="2007-01-29T09:49:53.114-05:00"
>> last-modified="2007-01-29T09:49:53.114-05:00" owner="admin" group="dba"
> Well yes, it would. You pass GET parameters (as your next example does) to
> any http host by query-value pairs, linked by equals signs. You have no
> equals sign there, hence eXist sees no query and returns you the basic
> metadata for the context collection only
Thanks, and I was hopeful that correcting the typo would help, but even
no results, and there are many div1 elements in the xml file. Yet this
returns the whole file (there's only one in the collection). So REST is
>> Yet the example
>> collection of the shakespeare/plays/macbeth.xml does return elements and
>> their content:
>> (althought certainly not all, as I understand XQuery's // path should.
> You mean that you aren't getting all STAGEDIR nodes in all documents in the
> Shakespeare collection? I do on my now somewhat out-of-date installation. So
> if it isn't happening for you, that may be a regression.
Could you explain what you mean by a regression? BTW: this server is
online, so if you have the time to quickly try that URL, it might
illustrate the behavior. Running on Mac OS X 10.4.x.
>> Could this be an index issue?
> Unlikely. Index problems effect only the execution speed of standard XPath
> expressions like yours, not their correct execution. The only instances in
> which an index problem can cause results that should be returned not to be
> found is if you are using eXist's non-standard fulltext extension operators
> or functions.
>> Is there any tutorial or better documentation showing example REST-style
>> GET with xquery AND what one ought to expect for output?
> Shouldn't be needed. The whole point of a REST interface is that you don't
> need to know much about it beyond how to do basic HTTP transactions. What
> eXist-specific things there are re permitted/required parameters and their
> values are already fully documented. As for what you should expect: you
> should expect to get back, preceded by standard HTTP headers of course,
> which a browser will normally act as appropriate on but not display, nothing
> more or less than the correct result of the XQuery you submitted (the REST
> interface being in that sense completely transparent). In other words, HTTP
> headers aside, exactly what the same XQuery returns if submitted via the
> command-line client.
Thats good to hear. It should be transparent, once I get it to click.
BTW using the Query Dialog in the java admin client, I get the same
behavior: not all returns in the shakespeare, and no returns in my own
> Michael Beddow
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> Exist-open mailing list