On Thu, Jan 15, 2009 at 9:33 PM, Diego Marin Santos <[email protected]> wrote: > i didn't understand why this property has its onParentVersion set to IGNORE. > For example, let N be a versionable node and have the nt:resource node type. > Suppose N holds a file F with lastModified holding the value A. Now, I check > in a new version of N and this property wont be stored in VN (version of N > stored in your version history). Let's make N hold the same file F (with > lastModified holding the value B) and after restoring VN. How > jcr:lastModified has its onParentVersion set to IGNORE, this property of the > current N will be remain and not be removed, that is, the first version of F > had its lastModified property with the value A, and now has this property > set to B, the value of the second version. Does it make sense?
Not sure about the reasoning behind that decision, but you are right, it seems a bit weird when a restore happens. Nevertheless, you can define your own node type to be used as the jcr:content child of nt:file if you'd like a different behaviour. Regards, Alex -- Alexander Klimetschek [email protected]
