WG: Still Stuck with Versioning

[Thomas Kratz <th...@eiswind.de>]

I investigated somewhat further.

 

Now I have made the nt:file child versionable, the versioned parent node of
nt:unstructured truly has a child of nt:file but I don't get it right. The
nt:file child has no neither a uuid (as the original node has)  and is not
of nt:frozenNode (what I would have expected). I would expect to see
frozenNodes as children of my VersionHistory node ???

 

What I need is a versioned nt:unstructured that has versioned children of
nt:file. How would I do this ?

 

Regards Thomas

 

 

 

 

Von: Thomas Kratz [mailto:thomas.kratz@eiswind.de] 
Gesendet: Sonntag, 23. November 2008 12:40
An: 'users@jackrabbit.apache.org'
Betreff: Stuck with Versioning

 

Hi,

 

I'm trying to get going with some simple Versioning. I ve been struggling
for six hours now and since I'm not getting along with google I hope someone
can help me.

 

I have nodes of nt:unstructured, that have nt:file childnodes with
corresponding nt:resource nodes.

 

To be honest I don't have a clue if this is a good strategy at all.Basically
I need to store files with some attributes that are subject to change.

 

Now I want the containing nt:unstructured node to be the root of a versioned
subtree. I added mix:versionable, that's fine, but the child nodes don't get
versioned. I found some information on default OPV, so I tried to add
mix:versionable to the child nodes. Don't know if this is a good idea.

 

Now I strangely already have a strange Version when I first save the
nt:unstructured (don't understand that at all). When I create a new version
of the node, it now seems to have nt:file child but that still lacks an
jcr:content property.

 

If I can get any hints on existing documentation or if my concept makes
sense at all that would be gladly appreciated.

 

Regards Thomas

Re: WG: Still Stuck with Versioning

[Julian Reschke <ju...@gmx.de>]

Thomas Kratz wrote:
> I investigated somewhat further.
> 
>  
> 
> Now I have made the nt:file child versionable, the versioned parent node of
> nt:unstructured truly has a child of nt:file but I don't get it right. The
> nt:file child has no neither a uuid (as the original node has)  and is not
> of nt:frozenNode (what I would have expected). I would expect to see
> frozenNodes as children of my VersionHistory node ???
> 
> ...

The nt:versionHistory node should have child nodes of type nt:version.

BR, Julian