Hi,
On 09/12/10 15:54, Clemens Wyss wrote:
I create a copy of a jackrabbit repository with
org.apache.jackrabbit.core.RepositoryCopier (using
org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager).
Trying to access this copy with
org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager
fails.
Testcase:
1) create a repository.xml file with
org.apache.jackrabbit.core.persistence.pool.DerbyPersistenceManager
2) start/stop jackrabbit
3) change repository.xml to
org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager
4) start jackrabbit
I don't understand why pooled access should yield different persisted
data...
Bug or feature?
Bug, the only difference between these persistence managers should be
the way they manage the database connection.
Can you file an issue about this with more details like the exact error
messages you're seeing and the Jackrabbit version you're using?
BR,
Jukka Zitting
