I think you are on the right track. After extensively looking through source
code it looks like jackrabbit has references to my ng:file node along with
the jcr:versionHistory and jcr:baseVersion etc... My question is: Where is
my app storing this version information if I potentially have the versioning
persistence manager set up incorrectly? Right now i have the
schemaObjectPrefix for my workspace and versioning set to the same value. I
am about to try having different prefixes, however, i assumed that the
persistenceManagers would use different table names even if the prefixes
are set to be the same. Do both persistenceManagers use the same table
names? The following is my repository.xml config. Please advise. Thanks!
<?xml version="1.0"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!DOCTYPE Repository PUBLIC "-//The Apache Software Foundation//DTD
Jackrabbit 1.2//EN"
"http://jackrabbit.apache.org/dtd/repository-1.2.dtd";>
<!-- Example Repository Configuration File -->
<Repository>
<!--
virtual file system where the repository stores global state
(e.g. registered namespaces, custom node types, etc.)
-->
<FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
</FileSystem>
<!--
security configuration
-->
<Security appName="testApp">
<!--
access manager:
class: FQN of class implementing the AccessManager interface
-->
<AccessManager
class="org.apache.jackrabbit.core.security.SimpleAccessManager">
<!-- -->
</AccessManager>
<LoginModule
class="org.apache.jackrabbit.core.security.SimpleLoginModule">
<!-- anonymous user name ('anonymous' is the default value) -->
<!--
default user name to be used instead of the anonymous user
when no login credentials are provided (unset by default)
-->
<!-- -->
</LoginModule>
</Security>
<!--
location of workspaces root directory and name of default workspace
-->
<Workspaces rootPath="${rep.home}/workspaces"
defaultWorkspace="default"/>
<!--
workspace configuration template:
used to create the initial workspace if there's no workspace yet
-->
<Workspace name="@wsp.name@">
<FileSystem
class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
</FileSystem>
<!-- PersistenceManager
class="org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager">
</PersistenceManager -->
<PersistenceManager
class="org.apache.jackrabbit.core.persistence.db.OraclePersistenceManager">
</PersistenceManager>
<!-- Causes an exception. need to figure out why.
<SearchIndex
class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
</SearchIndex>
-->
</Workspace>
<!--
Configures the versioning
-->
<Versioning rootPath="${rep.home}/version">
<FileSystem
class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
</FileSystem>
<PersistenceManager
class="org.apache.jackrabbit.core.persistence.db.OraclePersistenceManager">
</PersistenceManager>
</Versioning>
<!-- Causes an exception. need to figure out why.
<SearchIndex
class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
</SearchIndex>
-->
</Repository>
Marcel Reutegger wrote:
>
> just a wild guess, but can you please check if the persistence manager for
> versioning is configured properly. e.g. the schemaObjectPrefix should be
> something like:
>
>
>
> regards
> marcel
>
> bilobag wrote:
>> So after some more research I realized that it is throwing an exception
>> because for some reason jackrabbit is calling
>> SharedItemStateManager.getNodeReferences() to find a reference to one of
>> the
>> version history nodes. Now it looks like it checks the persistent
>> manager
>> first and then checks the virtual providers for a reference to this
>> version
>> node. Now, I am using an oracle db for my persistent mgr and when I
>> check
>> the REFS table, there are no rows in there. I know versionable nodes
>> contains reference properties, but it seems like they aren't stored in
>> the
>> database REFS table. Is this correct? So this error occurs when i try
>> to
>> remove my ng:file node which is versionable and contains an nt:resource
>> property. To me, it looks like either my repository isn't storing the
>> node
>> references in the db or virtual providers when i add the node, or when i
>> remove the ng:file node, the references get deleted and for some reason
>> jackrabbit tries to access them after they are deleted and can not save.
>> Please advise, i have been looking at this for days now. Thanks.
>
>
>
--
View this message in context:
http://www.nabble.com/Node-remove.--Removing-reference-property-problem.-tf4062111.html#a11579709
Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
