09-05-2012 12:17 PM
<types>
<!– Enterprise-wide generic document type –>
<type name="acme:doc">
<title>ACME Document</title>
<parent>cm:content</parent>
<properties>
<property name="acme:displayName">
<type>d:text</type>
</property>
<property name="acme:documentType">
<type>d:text</type>
</property>
<property name="acme:employeeID">
<type>d:text</type>
</property>
<property name="acme:category">
<type>d:text</type>
</property>
<property name="acme:subCategory">
<type>d:text</type>
</property>
<property name="acme:expirationDate">
<type>d:date</type>
</property>
<property name="acme:userNotes">
<type>d:text</type>
</property>
<property name="acme:keyWords">
<type>d:text</type>
</property>
</properties>
<property name="acme:userNotes">
<type>d:text</type>
</property>
09-07-2012 01:38 AM
<property name="acme:userNotes">
<type>acme:userNote</type>
<multiple>true</multiple>
</property>
(confirmed that this is supported by CMIS)
09-11-2012 12:18 PM
09-11-2012 10:33 PM
Along the idea you mentioned with storing a serialized text String representation of the object (JSON or XML for that matter), do you know if one could define the property type (instead of d:text, let's say) as a binary field where one could store a serialized object instance (a class that implements java.io.Serializable).
I see something called "content" as a type: http://wiki.alfresco.com/wiki/Type_Mech … erty_Types or am I misreading this?
Even though these data types are defined out of the box, if you wanted to change the Alfresco data type "text" so that it maps to your own custom class rather than java.lang.String, you could.
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.