[
https://issues.apache.org/jira/browse/JCR-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639635#action_12639635
]
Torgeir Veimo commented on JCR-1808:
------------------------------------
It appears the repository.xml I'm using with JR 1.5 is different than the one
used to create the 1.4.X repository. The new one declares the bundle
persistence manager. Changing to the old persistence manager for the 1.5
repository.xml makes things work again;
< <PersistenceManager
class="org.apache.jackrabbit.core.state.db.DerbyPersistenceManager">
< <param name="url" value="jdbc:derby:${wsp.home}/db;create=true"/>
< <param name="schemaObjectPrefix" value="${wsp.name}_"/>
---
> <PersistenceManager
> class="org.apache.jackrabbit.core.persistence.bundle.DerbyPersistenceManager">
> <param name="url" value="jdbc:derby:${wsp.home}/db;create=true"/>
> <param name="schemaObjectPrefix" value="${wsp.name}_"/>
> deploying 1.5.0-b1 with existing DB from 1.4.6 throws exception
> ---------------------------------------------------------------
>
> Key: JCR-1808
> URL: https://issues.apache.org/jira/browse/JCR-1808
> Project: Jackrabbit
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 1.5.0
> Environment: tomcat 6.0.14, jdk 1.5 OS X, derby persistence
> Reporter: Torgeir Veimo
> Priority: Blocker
> Attachments: log.txt, repository.xml
>
>
> Trying out the new jackrabbit build 1.5.0-b1 with an existing repository
> created with jackrabbit 1.4.*, throws exception on startup. Log output
> included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
