You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2008/01/09 11:21:33 UTC
[jira] Created: (JCR-1298) Wrong schemaObjectPrefix parameter in
default repository.xml
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.3, 1.3.1
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.
[jira] Commented: (JCR-1298) Wrong schemaObjectPrefix parameter in
default repository.xml
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557237#action_12557237 ]
Marcel Reutegger commented on JCR-1298:
---------------------------------------
Jukka wrote:
> We should probably disable filtering for most parts of src/main/resources.
to my knowledge you can not selectively filter, except when using separate resource directories. see previous comment.
> 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.
[jira] Commented: (JCR-1298) Wrong schemaObjectPrefix parameter in
default repository.xml
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (JCR-1298) Wrong schemaObjectPrefix parameter in
default repository.xml
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557249#action_12557249 ]
Jukka Zitting commented on JCR-1298:
------------------------------------
The resources-filtered idea seems OK to me.
> 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.
[jira] Commented: (JCR-1298) Wrong schemaObjectPrefix parameter in
default repository.xml
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557233#action_12557233 ]
Marcel Reutegger commented on JCR-1298:
---------------------------------------
This seems to be related to http://jira.codehaus.org/browse/MRESOURCES-3. The report is pretty confusing and the resolution does not say in what version the fix is.
> 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.
[jira] Resolved: (JCR-1298) Wrong schemaObjectPrefix parameter in
default repository.xml
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (JCR-1298) Wrong schemaObjectPrefix parameter in
default repository.xml
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557234#action_12557234 ]
Jukka Zitting commented on JCR-1298:
------------------------------------
We should probably disable filtering for most parts of src/main/resources.
> 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.