[daisy] Collection Cache

[TimDavid]

We're using Daisy to store content that is retrieved by a Grails server for
display in a web application.
The Grails server code is connecting to the remote Daisy repository server
and using the implementation of the Repository interface to retrieve
documents. 

We found that if a user creates a new Collection using the Daisy wiki
interface, and then modifies an existing document by adding it to the newly
created collection, the application server will encounter an exception the
next time the document is retrieved. The exception stacktrace starts like
this

org.outerj.daisy.repository.CollectionNotFoundException: The collection with
ID 31 does not exist.
at
org.outerj.daisy.repository.commonimpl.CollectionCache.getCollection(CollectionCache.java:74)
at
org.outerj.daisy.repository.commonimpl.CommonCollectionManager.getCollection(CommonCollectionManager.java:59)
at
org.outerj.daisy.repository.clientimpl.RemoteDocumentStrategy.instantiateDocumentFromXml(RemoteDocumentStrategy.java:87)
at
org.outerj.daisy.repository.clientimpl.RemoteDocumentStrategy.load(RemoteDocumentStrategy.java:57)
at
org.outerj.daisy.repository.commonimpl.CommonRepository.getDocument(CommonRepository.java:192)
at
org.outerj.daisy.repository.commonimpl.RepositoryImpl.getDocument(RepositoryImpl.java:143) 

My questions are:
1) Is there a way to configure the CommonCollectionManager running in the
application server JVM to gracefully detect the new collection and
automatically flush its cache?
2) Alternatively, can I disable the Collection cache?
3) Or do I need to set up the Grails application server to listen for events
detected by Daisy repository server and respond accordingly?

Thanks for any help or suggestions,
Tim
-- 
View this message in context: http://www.nabble.com/Collection-Cache-tp17344640p17344640.html
Sent from the Daisy - General mailing list archive at Nabble.com.