Hi,
Regarding the exceptions Jenya reported which occur on some occasions,
I've noticed exaclty the same exception when for example I run an
xupdate:remove on a selection which evaluates to an empty node set.
i.e. the first time, when there are nodes which match the select XPath, it removes them.
When no nodes are absent, it throws up exactly this exception.
Can anyone advise us about how (or indeed whether) Xindice could/should gracefully ignore
xu:remove attempts to remove nodes which have already been removed - without reporting errors
- or some elaborate workaround for dealing with this problem?
The specification of xu:remove states that the select expression must evaluate to a node-set.
IMHO, an empty node-set should be acceptable - and should result in no removals rather than an error.
Any ideas?
- Mark Harrison
Hi, I'm running example XUpdate, and some times I'm getting this exception:
org.apache.xindice.client.corba.db.APIException: IDL:org/apache/xindice/client/corba/db/APIException:1.0 at org.apache.xindice.client.corba.db.APIExceptionHelper.read(APIExceptionHelpe r.java:112) at org.apache.xindice.client.corba.db._CollectionStub.queryCollection(_Collecti onStub.java:833) at org.apache.xindice.client.xmldb.services.XUpdateQueryServiceImpl.updateResul t(XUpdateQueryServiceImpl.java:165) at org.apache.xindice.client.xmldb.services.XUpdateQueryServiceImpl.update(XUpd ateQueryServiceImpl.java:185) at org.apache.xindice.examples.XUpdate.main(XUpdate.java:32) XML:DB Exception occured 1 Query Processing Error
But, I'm sure I've run it successful few times. But I didn't make any changes just restart the xindice. What could it be?
Thanks Jenya
