Torgeir, thanks by your help. What is the difference between declare a xml file or a cnd file for nodetype definition? Is the file (xml or cnd) imported automatically or I have to place the file in a specific place and call some special method?
In the case of nodetypes mentioned, the cnd file would be: " // for the "my" namespace. <my = 'http://www.mycompany/my/1.0'> [my:timelife] mixin //I don't know if its the appropriate kind of node, but.... - my:timeini (date) mandatory - my:timeend (date) mandatory " and the xml file would be: " <?xml version="1.0" encoding="iso-8859-1"?> <nodeTypes xmlns:my="http://www.mycompany/my/1.0";> <nodeType name="my:timelife" isMixin="false" hasOrderableChildNodes="false" primaryItemName=""> <supertypes> <supertype>nt:resource</supertype> <supertype>nt:content</supertype> </supertypes> <propertyDefinition name="my:timeini" requiredType="Date" autoCreated="false" mandatory="true" onParentVersion="COPY" protected="false" multiple="false" /> <propertyDefinition name="my:timeend" requiredType="Date" autoCreated="false" mandatory="true" onParentVersion="COPY" protected="false" multiple="false" /> </nodeType> </nodeTypes> " Regards Helio >On Thu, 2006-03-09 at 14:43 -0300, hsp wrote: >> >> So, I think the "my:timelife" is mix (?), and the other child >> nodetypes are Date (I don't know who would be the parent for >> "my:timelife"). There are some more needs, but with this example I >> will mind the others. >> Could someone mount a simple xml example with the tree above? > >You can define a mixin nodeType with the my:timeini and my:timeend >values stored as properties. Then you can attach that mixin nodeType to >an existing node of your choice and add those properties. A mixin node >doesn't have any parent nodeType. In CND notation; > >[my:timelife] mixin >- my:timeini (date) mandatory >- my:timeend (date) mandatory > >-- >Torgeir Veimo > >
