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:
<param name="schemaObjectPrefix" value="version_"/>
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.
