Re: restore without persistence
We achieved this on a product using the frozen sub nodes of the version node (version object). Except for the renamed properties for the node types there is not much of a difference (of course this depends on how your node types are structure). This probably did not help much ... but at least it's achievable :) On Wed, 2006-07-26 at 17:16 -0400, David Kennedy wrote: > Is there a way to retrieve the "versions" of a node without actually > persisting them? Here, by "versions" I mean the actual instance of the > primaryNodeType and not the Version object. I'd like to be able to show > the differences between 2 versions of a node without having to restore the > one out of version storage (and replace the current node). > > David
Re: restore without persistence
Hi David, The state of the versionable node is stored in a subnode of the version node with the same name as the versionable, but of type nt:frozenNode. The frozen node itself is not an exact copy of the versionable, but all the information about the state of the versionable at version-time is recoverable. Have a look at the spec for more details. Peeter On 7/26/06, David Kennedy <[EMAIL PROTECTED]> wrote: Is there a way to retrieve the "versions" of a node without actually persisting them? Here, by "versions" I mean the actual instance of the primaryNodeType and not the Version object. I'd like to be able to show the differences between 2 versions of a node without having to restore the one out of version storage (and replace the current node). David
