You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2009/04/23 12:24:47 UTC
[jira] Commented: (JCR-2070) jcr-server should respect node type
definition jcr:content
[ https://issues.apache.org/jira/browse/JCR-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701881#action_12701881 ]
Jukka Zitting commented on JCR-2070:
------------------------------------
The problem with using addNode("jcr:content") without explicitly specifying a node type, is that by default the node would then end up with "nt:base" as it's node type if the parent is a standard "nt:file" node.
> jcr-server should respect node type definition jcr:content
> ----------------------------------------------------------
>
> Key: JCR-2070
> URL: https://issues.apache.org/jira/browse/JCR-2070
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-server
> Reporter: Michael Dürig
> Attachments: JCR-2070.patch
>
>
> When creating a new file, jcr:content defaults to nt:unstructured. This causes file creation to fail when the underlying persistent store (i.e. SPI implementation) does not support nt:unstructured for jcr:content.
> I suggest to check whether the underlying implementation provides its own node type for jcr:content and use that one. If not, default to nt:unstructured.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.