No, versioning works on node-level. Handling all the node's data together as one "bundle" (except for long binaries that should go into the DataStore) is the most efficient way to handle and store typical JCR data - that's why the bundle persistence managers work that way (storing one serialized bundle with one node and its properties).
Regards, Alex On Mon, Jul 28, 2008 at 7:41 AM, Sangeeta <[EMAIL PROTECTED]> wrote: > Hi > > I have node type with following structure. > book:file and book:folder extends book:node. > > When I make an node as node:file , is it possible to make property of > book:node non- versionable and property of book:file as versionable. > Basically user can change name, path title ...without making versions but > when book:content is changed, node should be versioned. > > > > [book:node] > nt:base > - book:name (string) mandatory > - book:path (string) > - book:title (string) > - book:nodeType (string) > - book:description (string) > - book:reportID (string) > - book:createdDate (date) > - book:publishedDate (date) > - book:unPublishedDate (date) > - book:region (string) > - book:department (string) > - book:language (string) > - book:organizationID (string) > - book:keywords (string) > - book:securityRoles (string)multiple > > [book:file] > book:node > - book:content (binary) > - book:contentTxt (string) > > > [book:folder] > book:node > + * = book:file multiple > > Thanks > Sangeeta > > -- Alexander Klimetschek [EMAIL PROTECTED]
