[
https://issues.apache.org/jira/browse/JCR-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557236#action_12557236
]
Marcel Reutegger commented on JCR-1298:
---------------------------------------
The only workaround I see is:
- move the repository.properties to a separate resources-filtered folder
- change the pom.xml
Index: pom.xml
===================================================================
--- pom.xml (revision 610328)
+++ pom.xml (working copy)
@@ -230,6 +230,9 @@
<resources>
<resource>
<directory>src/main/resources</directory>
+ </resource>
+ <resource>
+ <directory>src/main/resources-filtered</directory>
<filtering>true</filtering>
</resource>
</resources>
Does anyone have a better idea?
> 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
>
> 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.
