[ 
https://issues.apache.org/jira/browse/JCR-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969864#action_12969864
 ] 

Stefan Guggisberg commented on JCR-2839:
----------------------------------------

> To be clear, it's actually the reverse... 

mea culpa, sorry

justin is of course right

> 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.

Reply via email to