jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] Commented: (JCR-2070) jcr-server should respect node type definition jcr:content
Date Thu, 23 Apr 2009 11:25:47 GMT

    [ https://issues.apache.org/jira/browse/JCR-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701900#action_12701900

Michael Dürig commented on JCR-2070:

getContentNodeType() is hardcoded to nt:unstructured in DefaultHandler. So the current code
always tries to create jcr:content with type nt:unstructured. This fails if the parent's child
node definition does not allow nt:unstructured for jcr:content (i.e. requires nt:resource).

As Jukka noted, the patch is flawed. 

> 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.

View raw message