Could this be caused by the fact that the cache is defined at the
servlet level, instead of the application level? Just a hypothesis.
As a quick fix for your problem (but not such a good idea) would be to
flush the cache after each xmlrpc store action.
On 6/15/07, Thomas Drevon <thomas.drevon(a)intermedia.uio.no> wrote:
Hi!
We're experimenting with xmlprc calls to xwiki (using code from
http://www.xwiki.org/xwiki/bin/view/UserGuide/XMLRPCExample), and are
encountering some strange behaviour:
A newly created document will appear directly in xwiki as expected.
However, when we update this newly created doc the database is updated,
but when we view the page in xwiki, we still see the old doc. If a
restart of tomcat is done, the updated doc appears as expected.
It seems as if xwiki is sticking more closely to it's cached verion of
what's in the database than what we would prefer. And it looks very
similar to what I discovered while editing tags on blog entries.
Is this behaviour considered a bug? Is there any code that can be invoke
in order to re-read the object in question from the database?
Once again, any help would be greatly appreciated.
Sergiu Dumitriu
--
http://purl.org/net/sergiu