From: Jon Williams <jon@sh...> - 2003-02-18 16:57:35
I've been using eXist for awhile now (since 0.7)
so I've become fairly comfortable...
I've just upgraded my CMS to eXist 0.9, and I'm
still having a problem that's remeniscent of issues
I've had with every version I've used thus far.
I'm using eXist to store my content docs, and a combination
of xsp and xsl to pull (myquery.xsp), modify (output of myquery.xsp
is processed by modifier.xsl), and replace ( all of which is dumped
back into exist by modify.xsp) the changed document.
This works great.
Oddly though, a query meant to return the entire contents of a
will (intermittently?) fail when the <xmldb:results> iterator attempts
include the (now) modified file (via <xmldb:get-xml as="xml"/> ).
<xmldb:document-name /> shows up, but get-xml is empty.
You'd think that this represented a problem with the query-modify-store
but if you query the file directly via
...it's as you'd expect.
If I restart the server or mutter the right incantations (or
profanities), everything starts
working again until i try to modify a file...
It's acting suspiciously like some sort of caching or flushing issue. I
in xadmin.xsp -- but i don't see any documentation on it, so I'm not
sure if or
where I'd need to add it...
I've purposefully not attached code -- there's a fair number of (short)
Please let me know if there's anything you'd like to see.
I'm really anxious to get this working more smoothly.
Anything ya'll can offer would be greatly appreciated...
Get latest updates about Open Source Projects, Conferences and News.