Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1027351402.1240496370315.JavaMail.jira@brutus>
Date: Thu, 23 Apr 2009 07:19:30 -0700 (PDT)
From: =?utf-8?Q?Michael_D=C3=BCrig_=28JIRA=29?= <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-2070) jcr-server should respect child node
 definition of jcr:content
In-Reply-To: <1598770186.1239709934953.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JCR-2070?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D127019=
45#action_12701945 ]=20

Michael D=C3=BCrig commented on JCR-2070:
------------------------------------

Yes you're right. I see two options:=20

1) Check whether any of getPrimaryNodeType() or getMixinNodeTypes() allows =
for adding the jcr:content node of the given type. If so create it. Otherwi=
se try to create jcr:content without explicitly specifying a node type.=20

2) Try to create jcr:content with the given type. On RepositoryException re=
try without explicitly specifying a node type.=20

For 1) the supertypes should theoretically also be considered. However for =
a compliant repository implementation they can be ignored I think. 2) is mo=
re general since it just retries regardless of why adding failed on the fir=
st try.=20

WDYT?

> jcr-server should respect child node definition of 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=C3=BCrig
>         Attachments: JCR-2070-1.patch, JCR-2070.patch
>
>
> When creating a new file, jcr:content defaults to nt:unstructured. This c=
auses file creation to fail when the underlying persistent store (i.e. SPI =
implementation) does not support nt:unstructured for jcr:content.=20
> 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:unstruct=
ured.

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