Hello, the cache of StandardStore is not always cleared, if the transaction was rolled back.
I do not understand completely, what is happening, but its looks like this. Clearing will work, if the callback is caused by a exception in a child store. In this case, the child store will be delisted from the transaction with success == false, which causes the StandardStore to clear the cache. However, if the rollback is initiated by an external source, for example by an exception, which is thrown by a ContentInterceptor and catched in AbstractWebdavServlet, the StandardStore will never be informed of this, because it is not enlisted in the transaction itself. I suggest the following solution: Delegate caching from StandardStore to wrappers around NodeStore et al. Since those wrappers are enlisted in the transaction itself, they will be notified, if the transaction is rolled back. Martin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
