Re: RE: Secondary Type example from opencmis doc throws type unknown error

Thank you so much for very insightful response, Jeff. I'll raise this. But it will be hard to switch to different technology now as we have some other functionality implemented with CMIS. It may be overcomplicating the problem. But if possible I would still try storing multiple secondary types

RE: RE: RE: Secondary Type example from opencmis doc throws type unknown error

>> do you define new type e.g. PropertyList (key,value), and create objects with that type and then relationship between document and that type? >> I meant this way exactly, so with PropertyList type and property definitions key, value, then use this to query to get the "cmis:objectId" and then

Re: RE: Secondary Type example from opencmis doc throws type unknown error

Based on the flexibility you need, including querying capabilities, I wouldn't use a CMIS repository to persist this data. I would use a NoSQL document store. Then, depending on the implementation selected, I'd have full schemaless capabilities to store any data in any structure as needed. One of

Re: RE: RE: Secondary Type example from opencmis doc throws type unknown error

That sounds really interesting. Do you mean to create table (SQL DDL) in db schema? Or do you define new type e.g. PropertyList (key,value), and create objects with that type and then relationship between document and that type? Thanks Krzysztof On 2017-10-11 18:24, "Suhaib Fahad"

RE: RE: Secondary Type example from opencmis doc throws type unknown error

Secondary types are not helpful in querying with the use-case you have specified, It looks like you need a 'cmis:relationship' between two types like a Master-Detail table in DBs, and the Detail table will have Key/Value pairs (for the dynamic field data) that you would use to specify a JOIN and

Re: RE: Secondary Type example from opencmis doc throws type unknown error

Thanks for reply. The question would be how should i name these properties, since they are not known upfront? They are derived from client input. I have an idea to define a secondary type with two properties: key and value. and store my dynamic property there. Is it possible to store a

Re: Secondary Type example from opencmis doc throws type unknown error

Is there another way of storing key-value pairs on documents that are not known upfront? i.e. to store a property that was not defined before? Krzysztof On 2017-10-11 16:39, Jeff Potts wrote: > They are not dynamic. A secondary type must already be known by the >

Secondary Type example from opencmis doc throws type unknown error

Hello All, I was wondering how the secondary type work. They are meant to be dynamic, so when you should be able to create them on the fly. however, when i run example from the docs, i get CmisObjectNotFoundException: Type 'custom:classifictaion' is unknown! do you need to predefine the

Re: Copy document with version history

i had to upgrade to 0.11.0 version and remove org.alfresco.cmis.client.impl.AlfrescoObjectFactoryImpl from session properties. On 2017-10-11 14:00, "krzysztoffzielin...@gmail.com" wrote: > are there minimum chemistry openscmis client library and alfresco opencmis

Re: Copy document with version history

are there minimum chemistry openscmis client library and alfresco opencmis extesnion versions to be used with browser binding? I use versions: 0.6.0 and 0.4 respectively, which may be a root cause of my issues. On 2017-10-10 12:32, Florent Guillaume wrote: > Please