I have a feeling this is in relation to another bug e-mail subject '
Something quite wrong on ResourceSet getResource (or removeResource) for
index 0' which Wolfgang verified awhile back is a bug.
You can call RemoveResource but it seems
getMembersAsResource().getContent() was still showing all the
Resources. Hence a ResourceSet of 200 I called removeResource to get it
down to 50 which worked but then when printing out the contents using
getMembersAsResource().getContent().toString() I saw all 200 again.
Happens when connecting to an external eXist via my webapp.
Get latest updates about Open Source Projects, Conferences and News.