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 <jeffpott...@gmail.com> wrote: > They are not dynamic. A secondary type must already be known by the > repository before it can be applied. > > Some repositories support using CMIS to add type and secondary type > definitions to the repository. Once the repository registers your > definition you can then use it. But you cannot simply make up a content > model and start using it without registering it first, otherwise you will > get type unknown errors, as you have seen. > > Jeff > > On Wed, Oct 11, 2017 at 10:15 AM, krzysztoffzielin...@gmail.com < > krzysztoffzielin...@gmail.com> wrote: > > > 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 "custom" namespace? > > > > Thanks a lot > > Krzysztof > > >
