Hi all, Right now, the OCM framework is supporting the mixin node type for different purposes (versionning, locking, ...). It is possible to specify the desired mixin node types into the class descriptor but today the ocm persistence manager cannot assign dynamically a new mixin node type to an object.
Do you see some interesting use cases that requires a dynamic support ? If yes, how the ocm persistence manager can map the mixin node type properties and child nodes into the object attributes ? All ideas are welcome. I would like to know if the current support is sufficient for the first OCM release. br, Christophe
