[ https://issues.apache.org/jira/browse/JCR-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved JCR-1298. ----------------------------------- Resolution: Fixed Fix Version/s: 1.4 Fixed in trunk (610372) and 1.4 branch (610377). > Wrong schemaObjectPrefix parameter in default repository.xml > ------------------------------------------------------------ > > Key: JCR-1298 > URL: https://issues.apache.org/jira/browse/JCR-1298 > Project: Jackrabbit > Issue Type: Bug > Components: jackrabbit-core > Affects Versions: 1.3.1, 1.3.3 > Reporter: Marcel Reutegger > Priority: Minor > Fix For: 1.4 > > > The object schema prefix is hard-coded in the default configuration file (I > think this taken from the jackrabbit-core.jar): > <PersistenceManager > class="org.apache.jackrabbit.core.persistence.bundle.DerbyPersistenceManager"> > <param name="url" value="jdbc:derby:${wsp.home}/db;create=true"/> > <param name="schemaObjectPrefix" value="Jackrabbit Core_"/> > </PersistenceManager> > This is probably caused by JCR-945, though I've no idea why ${wsp.name} is > replaced with the name of the module... > I have marked this issue as minor because it still works with the > DerbyPersistenceManager. There are separate database instances for each > workspace, but it will become a problem if a data base persistence manager on > a dedicated server is used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.