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 2006/10/26 11:34:16 UTC
[jira] Created: (JCR-605) Error when registering node types on
virgin repository
Error when registering node types on virgin repository
------------------------------------------------------
Key: JCR-605
URL: http://issues.apache.org/jira/browse/JCR-605
Project: Jackrabbit
Issue Type: Bug
Affects Versions: 1.1
Environment: svn 467288
Reporter: Marcel Reutegger
Priority: Minor
When a node type is registered on a repository that has never been started before an error is written to the log:
26.10.2006 10:36:02 *ERROR* [main] VirtualNodeTypeStateManager: Unable to index new nodetype: javax.jcr.ItemNotFoundException (VirtualNodeTypeStateManager.java, line 159)
Steps to reproduce:
> maven test:clean
> cp applications/test/repository/namespaces/ns_re.properties.install applications/test/repository/namespaces/ns_re.properties
> cp applications/test/repository/nodetypes/custom_nodetypes.xml.install applications/test/repository/nodetypes/custom_nodetypes.xml
Run test case o.a.j.init.NodeTypeData
It seems that the workspace initialization creates node states for jcr:system and a child node jcr:nodeTypes. The latter however is overlayed by a virtual node state provided by the VirtualNodeTypeStateProvider.
In case of an initial startup, the jcr:nodeTypes node is cached on creation and is not overlayed by the virtual twin from the VirtualNodeTypeStateProvider.
IMO the jcr:nodeTypes node state shouldn't have been created in the first place because it is overlayed anyway. The workspace initialization routine should only create a child node entry in the jcr:system node state but no actual child node state for that entry.
Opinions?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (JCR-605) Error when registering node types on
virgin repository
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-605?page=all ]
Marcel Reutegger reopened JCR-605:
----------------------------------
Assignee: Marcel Reutegger
The fix still tries to store the jcr:system node state in the regular workspace persistence manager.
> Error when registering node types on virgin repository
> ------------------------------------------------------
>
> Key: JCR-605
> URL: http://issues.apache.org/jira/browse/JCR-605
> Project: Jackrabbit
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: svn 467288
> Reporter: Marcel Reutegger
> Assigned To: Marcel Reutegger
> Priority: Minor
> Fix For: 1.1.1
>
>
> When a node type is registered on a repository that has never been started before an error is written to the log:
> 26.10.2006 10:36:02 *ERROR* [main] VirtualNodeTypeStateManager: Unable to index new nodetype: javax.jcr.ItemNotFoundException (VirtualNodeTypeStateManager.java, line 159)
> Steps to reproduce:
> > maven test:clean
> > cp applications/test/repository/namespaces/ns_re.properties.install applications/test/repository/namespaces/ns_re.properties
> > cp applications/test/repository/nodetypes/custom_nodetypes.xml.install applications/test/repository/nodetypes/custom_nodetypes.xml
> Run test case o.a.j.init.NodeTypeData
> It seems that the workspace initialization creates node states for jcr:system and a child node jcr:nodeTypes. The latter however is overlayed by a virtual node state provided by the VirtualNodeTypeStateProvider.
> In case of an initial startup, the jcr:nodeTypes node is cached on creation and is not overlayed by the virtual twin from the VirtualNodeTypeStateProvider.
> IMO the jcr:nodeTypes node state shouldn't have been created in the first place because it is overlayed anyway. The workspace initialization routine should only create a child node entry in the jcr:system node state but no actual child node state for that entry.
> Opinions?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (JCR-605) Error when registering node types on
virgin repository
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-605?page=all ]
Marcel Reutegger resolved JCR-605.
----------------------------------
Fix Version/s: 1.1.1
Resolution: Fixed
Fixed as proposed in svn revision: 469123
> Error when registering node types on virgin repository
> ------------------------------------------------------
>
> Key: JCR-605
> URL: http://issues.apache.org/jira/browse/JCR-605
> Project: Jackrabbit
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: svn 467288
> Reporter: Marcel Reutegger
> Priority: Minor
> Fix For: 1.1.1
>
>
> When a node type is registered on a repository that has never been started before an error is written to the log:
> 26.10.2006 10:36:02 *ERROR* [main] VirtualNodeTypeStateManager: Unable to index new nodetype: javax.jcr.ItemNotFoundException (VirtualNodeTypeStateManager.java, line 159)
> Steps to reproduce:
> > maven test:clean
> > cp applications/test/repository/namespaces/ns_re.properties.install applications/test/repository/namespaces/ns_re.properties
> > cp applications/test/repository/nodetypes/custom_nodetypes.xml.install applications/test/repository/nodetypes/custom_nodetypes.xml
> Run test case o.a.j.init.NodeTypeData
> It seems that the workspace initialization creates node states for jcr:system and a child node jcr:nodeTypes. The latter however is overlayed by a virtual node state provided by the VirtualNodeTypeStateProvider.
> In case of an initial startup, the jcr:nodeTypes node is cached on creation and is not overlayed by the virtual twin from the VirtualNodeTypeStateProvider.
> IMO the jcr:nodeTypes node state shouldn't have been created in the first place because it is overlayed anyway. The workspace initialization routine should only create a child node entry in the jcr:system node state but no actual child node state for that entry.
> Opinions?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (JCR-605) Error when registering node types on
virgin repository
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JCR-605?page=all ]
Marcel Reutegger resolved JCR-605.
----------------------------------
Resolution: Fixed
The jcr:system node is now created within the same method as the root node of the workspace: SharedItemStateManager.createRootNodeState().
In contrast to the previous initialization in RepositoryImpl.initWorkspace() the jcr:system node is created with just the two child node entries (one for jcr:versionStorage and one for jcr:nodeTypes), but the two child node state are not acutally created there because both are virtual states and already exist.
Fixed in revision: 469480
> Error when registering node types on virgin repository
> ------------------------------------------------------
>
> Key: JCR-605
> URL: http://issues.apache.org/jira/browse/JCR-605
> Project: Jackrabbit
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: svn 467288
> Reporter: Marcel Reutegger
> Assigned To: Marcel Reutegger
> Priority: Minor
> Fix For: 1.1.1
>
>
> When a node type is registered on a repository that has never been started before an error is written to the log:
> 26.10.2006 10:36:02 *ERROR* [main] VirtualNodeTypeStateManager: Unable to index new nodetype: javax.jcr.ItemNotFoundException (VirtualNodeTypeStateManager.java, line 159)
> Steps to reproduce:
> > maven test:clean
> > cp applications/test/repository/namespaces/ns_re.properties.install applications/test/repository/namespaces/ns_re.properties
> > cp applications/test/repository/nodetypes/custom_nodetypes.xml.install applications/test/repository/nodetypes/custom_nodetypes.xml
> Run test case o.a.j.init.NodeTypeData
> It seems that the workspace initialization creates node states for jcr:system and a child node jcr:nodeTypes. The latter however is overlayed by a virtual node state provided by the VirtualNodeTypeStateProvider.
> In case of an initial startup, the jcr:nodeTypes node is cached on creation and is not overlayed by the virtual twin from the VirtualNodeTypeStateProvider.
> IMO the jcr:nodeTypes node state shouldn't have been created in the first place because it is overlayed anyway. The workspace initialization routine should only create a child node entry in the jcr:system node state but no actual child node state for that entry.
> Opinions?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira