jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2793) Typo in NodeTypeRegistry
Date Thu, 21 Oct 2010 12:03:15 GMT

    [ https://issues.apache.org/jira/browse/JCR-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923415#action_12923415
] 

Jukka Zitting commented on JCR-2793:
------------------------------------

Thanks for the background! Yes, I see now that it's the removal of the BasedFileSystem layer
that's causing the problem. It would be cleaner though if either all or none of the FileSystem
implementations (including BasedFileSystem) supported paths without the leading slash. Anyway,
+1 to committing the patch as is.

> Typo in NodeTypeRegistry
> ------------------------
>
>                 Key: JCR-2793
>                 URL: https://issues.apache.org/jira/browse/JCR-2793
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>    Affects Versions: 2.2.0
>            Reporter: Serge Huber
>             Fix For: 2.2.0
>
>         Attachments: Fix_typo_on_custom_node_types_constant.patch
>
>   Original Estimate: 0.17h
>  Remaining Estimate: 0.17h
>
> It seems a little typo has been introduced in the NodeTypeRegistry, as illustrated in
this stack trace : 
> Caused by: javax.jcr.RepositoryException: internal error: invalid resource: nodetypes/custom_nodetypes.xml
> 	at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.<init>(NodeTypeRegistry.java:703)
~[jackrabbit-core-2.2-SNAPSHOT.jar:2.2-SNAPSHOT]
> 	at org.apache.jackrabbit.core.RepositoryImpl.createNodeTypeRegistry(RepositoryImpl.java:422)
~[jackrabbit-core-2.2-SNAPSHOT.jar:na]
> 	at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:294) ~[jackrabbit-core-2.2-SNAPSHOT.jar:na]
> This happens when using a DbFileSystem for the root filesystem. This didn't cause a problem
in 2.1.1
> The patch attached to this ticket correct the issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message