From: John P. <jv...@di...> - 2004-03-11 02:38:51
|
G'Day Everyone, just wanted to let you know that I fixed the problem below by placing = the following entry in the eXist configuration file: <index doctype=3D"root.element.name" default=3D"all" = attributes=3D"true"/> It was my understanding that all elements and attributes were indexed by = default, and that we only make such entries for exceptions, but it looks = like I was wrong. However, it seems the indexer still doesn't like an attribute value of = "-1". Thanks to Jean-Marc Vanel for his support. Cheers, John Polglase ----- Original Message -----=20 From: John Polglase=20 To: exi...@li...=20 Sent: Wednesday, March 10, 2004 1:20 PM Subject: Problem with retrieval via simple XPath query G'Day Everyone, We run an embedded eXist 1.01b1 on XP Pro, and the following problem has = persisted for snapshots 20040204 through 20040302: We load, for example, three validated xml resources into eXist. Each = has the same xml data model but different data. Before each load we = increment a root element attribute value. We retrieve these resources individually via the equivalent of: ResourceSet rs =3D = xqs.query("/root.element.name[@attribute.name=3D\"nn\"]"); where xqs =3D (XPathQueryService)coll.getService("XPathQueryService", = "1.0"); ... etc. This worked fine for all three resources until snapshot 20040204, but = now we can only retrieve the last resource uploaded. Although we have = re-sequenced the resource load, it is always only the last one loaded = that can be retrieved this way. However, the other two resources are = definitely in the database and can be retrieved via non-XPath means. Perhaps related to the above is that before snapshot 20040204 we used to = use a value of "-1" as a default value for the same root element = attribute. However, we had to abandon this value as, since snapshot = 20040204, we couldn't retrieve with it via Xpath at all. Any insight will be appreciated, John Polglase |