Here's a patch against eXist-0.9.1 to fix the case where ResourceSetImpl
sets the wrong parent Collection on a Resource when doing a remote XPath
query. The parent collection was always set to the collection of the
XPathQueryService that created the ResourceSet, which may not be correct
(the Resource may be in a sub-collection).
I'm not sure if the patch is correct, but it works here. Does the doc
String always contain the full doc path? And does something similar need to
be fixed for the last case in getResource ("value")?
SINTEF Telecom and Informatics