Jukka Zitting wrote:
Hi,Could you solve your use case simply by defining a custom versionable subtype like the following? [myns:versionable] > mix:versionable mixin - myns:versionComment (STRING) COPY The myns:versionComment property would be just a normal string property of the content node being versioned. Whenever the node is checked in, the comment property gets copied to the frozen node. So to associate a comment with a version, you'd do something like this: node.setProperty("myns:versionComment", "foo"); node.save(); node.checkin(); BR, Jukka Zitting
Yes, we do something like this. Since everything gets copied to the frozen node, you can have any number of version metadata properties you need.
Carlos
