It worked for me in a much older version of Xindice well about a year ago. I suggest that you try to get some of the XUpdate examples to work. I noticed a couple of things in your update query that might be problematical: 1. Some namespaces used in the query, and no namespace prefixes in the xpath used for select=. If your documents use namespaces, this won't work, because xpath steps whose names do not contain prefixes are assumed to be elements or attributes in *no* namespace (not the default namespace). If you need to put in namespaces, you also need to provide some namespace context (so the prefixes can be resolved to namespaces). I don't remember how to do this, but it is probably documented. If your documents use namespaces, you also have to worry about whether elements and attributes are qualified or not, as this also affects where or whether prefixes are needed in the xpaths. 2. When you query xindice, you cannot extract an attribute without its containing element. It may be that this limitation extends to XUpdate as well -- worth checking in the docs. This is why I recommend trying to get some documented example to work whose query is known to be OK, before moving on to your own uncharted territory.
Jeff ----- Original Message ----- From: "Julie McCabe" <[EMAIL PROTECTED]> To: <xindice-users@xml.apache.org> Sent: Friday, July 18, 2003 7:16 AM Subject: XUpdateQueryService work around Hello, Has anybody got xupdate:modifications working with XUpdateQueryService? is there a known list of problems as I cant get it working for a number of collections. The work around I've had to do is query for the resource, get the content, modify it using Java (substring etc) then remove the resource from the database and create a new resource with the modified content. I would prefer to use XUpdateQueryService for simplicity and scalabilty but its falling over on a 641 error - as mentioned in a previous mail to the list. My config is Java 1.4.1 and Xindice 1.1b1. Thanks Julie
