has anybody configured jackrabbit to use a single database for all repository and workspace filesystems and persistence managers?
i'm trying out a configuration that uses a single derby db for all of jackrabbit. this seems easier to manage than five separate databases. this setup seems to function ok until the repository is shutdown. at this point it looks like the first filesystem or persistence manager to be closed closes the derby connection, causing the next component's close to fail. are there any concerns about using a single unified database? what might be a good strategy for modifying jackrabbit to support this configuration? perhaps SimpleDbPersistenceManager and DbFilesystem should simply ignore closed connections when shutting themselves down?
