Mapping d:content in CMIS

[victorba]

Hello,

I am migrating a connector API from JSR-170+Jackrabbit to CMIS. The application have a custom model, where two properties are "d:content" type.

As I can see, CMIS don't map d:content properties, so it can't be read or write with CMIS connector. Do you know how to have more than one content per document? Renditions are a solution for this problem?
And, how can I make visible the content stored in that two properties? Making a process and converting that content in renditions would be a solution?

Thanks!

[kaynezhang]

I'm afraid you can't do it using alfresco open cmis extension,cmis dose not support document with two properties with  d:content type. but you can do it with alfresco native webservice or data webscript api.
You can do it like this
define an custom type that inherit cm:content type and add a property of type d:content,or define a custom aspect with a property of type d:content and apply it to cm:content type .
Then operate this type or aspect with alfresco native webservice or data webscript api.

[victorba]

thanks kaynezhang.

As I could see, Alfresco native webservice is no longer developed, and all work and effort is moved to CMIS, this is the comment in alfresco WIKI: "Please note that this API has been superceded by CMIS (specifically, the CMIS SOAP binding). It's use is no longer recommended.".
I don't know if it's a good idea start a new API over something that is marked as deprecated, because maybe in new versions of Alfresco something will stop working.

That means that in future, CMIS will never offer compatibility with d:content type? What happens with people that had this type in some property in their custom content model? They would never be able to use CMIS?

Thanks!

[kaynezhang]

Now in cmis1.1 specification a document object at most have one content stream,and we could only add string/boolean/decimal/integer/datetime/uri/id/html/ property type to a custom Type or second Type.It dosen't support add content property to cmis object.
Maybe  CMIS 2.0 or higher version will offer compatibility with d:content type.But now if you want add d:conent type to your  custom content model,you can't use cmis api.