No comment - You can add them. Thanks, Christophe
On 11/20/05, Oliver Kießler (JIRA) <[EMAIL PROTECTED]> wrote: > [ > http://issues.apache.org/jira/browse/GRFT-67?page=comments#action_12358104 ] > > Oliver Kießler commented on GRFT-67: > ------------------------------------ > > Here is a list of additional attributes that are needed for jcr node type > creation from the jcr-mapping file: > > class-descriptor > - jcrSuperTypes (comma separated list of jcr node supertypes) I am not so > sure if this should be used, we might end up with conflicts...) > > field-descriptor > - jcrType (jcr type that is supposed to be used, if the jcr-node management > has access to the java class I could use reflection but is that always the > case? Maybe the java classes are not in the classpath during node type > creation...) > - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping > file > - jcrMandatory (boolean) default is "false" if not specified in jcr-mapping > file > - jcrOnParentVersion default is "IGNORE" if not specified > - jcrProtected (boolean) default is "false" if not specified > - jcrMultiple (boolean) default is "false" if not specified > > bean-descriptor: > - jcrNodeType (defines the child node type) > - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping > file > - jcrMandatory (boolean) default is "false" if not specified > - jcrOnParentVersion default is "IGNORE" if not specified > - jcrProtected (boolean) default is "false" if not specified > - jcrSameNameSiblings (boolean) default is "false" if not specified > > collection-descriptor: > - jcrNodeType (defines the child node type) > - jcrAutoCreated (boolean) default is "false" if not specified in jcr-mapping > file > - jcrMandatory (boolean) default is "false" if not specified > - jcrOnParentVersion default is "IGNORE" if not specified > - jcrProtected (boolean) default is "false" if not specified > - jcrSameNameSiblings (boolean) default is "false" if not specified > > I think that's it. There are more attributes in the jackrabbit nodetypes xml > file and the JCR spec but I think these are the attributes that are sufficant > for jcr-mapping and jcr-nodemanagement. Please comment if these attributes > can be added to the jcr-mapping file or if I missed something... > > > Definition of Nodetype Management API > > ------------------------------------- > > > > Key: GRFT-67 > > URL: http://issues.apache.org/jira/browse/GRFT-67 > > Project: Graffito > > Type: Task > > Components: JCR-Nodemanagement > > Versions: 1.0-a1-dev > > Reporter: Oliver Kießler > > Assignee: Oliver Kießler > > Fix For: 1.0-a1-dev > > > > > Definition of the "nodemanagement API" in the > > org.apache.portals.graffito.jcr.nodemanagement.NodeTypeManager interface. > > -- > 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 > >
