[jira] Resolved: (JCR-2839) o.a.jr.c.p.pool.DerbyPersistenceManager not "compatible" with o.a.jr.c.p.db.DerbyPersistenceManager

["Stefan Guggisberg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCR-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Guggisberg resolved JCR-2839.
------------------------------------

    Resolution: Not A Problem

o.a.jr.c.p.pool.DerbyPersistenceManager is a SimpleDbPersistenceManager
(every node and property is stored in a single record)

o.a.jr.c.p.db.DerbyPersistenceManager is a BundleDbPersistenceManager
(a node and its properties are 'bundled' in 1 record)

apparently, they use different schemas to store the content. they were 
never meant to be compatible.

> o.a.jr.c.p.pool.DerbyPersistenceManager not "compatible" with o.a.jr.c.p.db.DerbyPersistenceManager
> ---------------------------------------------------------------------------------------------------
>
>                 Key: JCR-2839
>                 URL: https://issues.apache.org/jira/browse/JCR-2839
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>    Affects Versions: 2.1.1, 2.3.0
>            Reporter: Clemens Wyss
>
>  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
> or vice versa

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.