Hi Kimbro,
> >> There were some changes in XUpdate as far as namespaces go,
> >> but it shouldn'
> >> t have affected this. Can you send a sample document that the
> >> query should
> >> succeed against?
> >
> > Here you go. I think there might be a problem with my code, though,
> > because I can't make it work with DbXML now either.
> >
>
> Ok, please verify it before I start digging. :-)
I have turned the code in every direction, and can't find anything wrong with
it. I also tried a bit of digging myself, and this is what I came up with:
org.omg.CORBA.portable.ApplicationException
at
com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:390)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
at
org.apache.xindice.client.corba.db._CollectionStub.queryCollection(_CollectionStub.java:820)
at
org.apache.xindice.client.xmldb.services.XUpdateQueryServiceImpl.updateResult(XUpdateQueryServiceImpl.java:170)
This is the basic exception - I took a look at the XUpdateQueryServiceImpl
code, and it seems that in this line:
> EncodedBuffer buffer = col.queryCollection("XUpdate", commands,
> getNamespaces(), -1);
getNamespaces() is returning nothing - is this correct? Is the XUpdate
namespace somehow implicit?
The 'commands' parameter seems fine - it is exactly the same as the XUpdate
query I constructed, i.e.
<xupdate:modifications version="1.0"
xmlns:xupdate="http://www.xmldb.org/xupdate";> <xupdate:update
select="/data[userID='9' and
scoID='35327']/cmi/core/score/raw/value">15</xupdate:update>
</xupdate:modifications>
I'm not clear what happens after this call (I'm not familiar with Corba and the
code doesn't mean much to me). I do know, though, that the node referred to
exists (I query it immediately before the attempted update, and I can see it
with XindiceBrowser).
Any thoughts?
Thanks,
John
