Ahh, I've just noticed that ResourceSet allows random access to the
items in the set, which helps me understand why the current
implementation is
not very robust. Of course we could always ignore the getResource(index)
method of ResourceSet
;>
Perhaps I should take me questions to XmlDB, sic
I've not yet seena way to specify my XPath should return only keys
instead of documents or doc fragments -do you have more info on this?
Anyway, this only delays the problem, eventually even your list of keys
might be too long.
What is needed is a service which tages some paging parameter, let's
The problem is that the ResourceSetImpl iterates over the
results, adds each resource in the result as a child node of a single
result document,
turns that document into a String, and then uses the String to
produce an XMLResource that is the result sent back to the
client.
This blows up when the
[EMAIL PROTECTED] wrote:
Has anyone written a better iterator service for Xindice/Xml:db to get
over the limitation of throwing an out-of-memory exception if your
Xpath query returns too many results?
It seems that the default behaviour for Xindice at least, is to return
ALL the results in the R
