Do I understand correctly: if a have a custom (my own) type inherited from dm_cabinet – I cannot use this type to create a new Cabinet?
Is that so?
How are you creating the custom cabinet - via DFC, DFS, or Webtop/DA? If by code, then you may be able to instantiante the class. Not sure if Webtop/DA is hardcoded to create dm_cabinet type - should be easy to try.
As far as I remember, in Webtop, the New Folder component allows selecting sub types of dm_folder if there's any so I'd expect the same when creating a Cabinet..
As Johnny said, easy to test...
"so I'd expect the same when creating a Cabinet.." - NO. In Documentum Developer Edition 6.6 I use the combo-box 'Type:' in New Cabinet form is disabled. This is why I have posted this discussion, to understand - can I really meet a cabinet created as a dm_cabinet-derived type.
You need to cutomize WDK to achieve this.
In Documentum Developer Edition 6.6 I use the combo-box 'Type:' in New Cabinet form is disabled
But from your assertion "If by code, then you may be able to instantiante the class" I understand - this is possible programamtically, correct?
If so, an application I am developing (it browses Cabinets of a Documentum server) should taking this into account. The application uses DFS - a Query like 'select r_object_id from dm_cabinet'. My question is: will this bring also Cabinets of such dm_cabinet-derived types? 'select r_object_id from dm_folder' does bring also Folders of dm_folder-derived types - I saw this. So the 'select r_object_id from dm_cabinet' should behave the same?
Yes. DQL syntax takes care of derived types when you perform a select query.
