You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@jackrabbit.apache.org by harvey waters <ha...@googlemail.com> on 2007/03/21 13:29:51 UTC

Version Configuration Confusion

I'm setting up some nodes to do the following...

Node A
|                |              |
|                |              |
Node B      Node C    Node D

Is is possible...

1) to delete B and then restore Node A (in order to restore B), without
affecting the state of C

2)  to delete Node B, then delete Node D, and restore A (to resore Node B)
but without restoring Node D

Finally, does anyone know if it is possible to un-delete a node without
having to restore the parent node. Perhaps find the version using xpath and
then restore it somehow?

Help much appreciated.


Thanks

Harvey

Re: Version Configuration Confusion

Posted by HarveyWaters <ha...@googlemail.com>.

thanks for that, I'll give it a try.

I've also had a problem restoring a node which has a mixin added to it at
runtime. If i restore to a version before the mixin version was added then I
get a ConstraintViolationException ( as the mixin has a mandatory property
on it). I thought the mixin's were stored as part of the forzenNodeType so
mixins in later versions would simply not exist when the version without the
mixin was restored ?

Thanks for the help.





Tobias Bocanegra wrote:
> 
> hi,
> if b,c and d have OPV=Version you can do those operations.
> to "undelete" a node, you need to know the version you want to restore,
> and
> use the Node.restore(Version version, String relPath, boolean
> removeExisting)
> method. eg: "A".restore("version of B", "B", false);
> 
> or you can restore it to a complete different parent, eg:
> "someparent".restore("version of B", "newname", false);
> 
> regards, toby
> 
> On 3/21/07, harvey waters <ha...@googlemail.com> wrote:
>> I'm setting up some nodes to do the following...
>>
>> Node A
>> |                |              |
>> |                |              |
>> Node B      Node C    Node D
>>
>> Is is possible...
>>
>> 1) to delete B and then restore Node A (in order to restore B), without
>> affecting the state of C
>>
>> 2)  to delete Node B, then delete Node D, and restore A (to resore Node
>> B)
>> but without restoring Node D
>>
>> Finally, does anyone know if it is possible to un-delete a node without
>> having to restore the parent node. Perhaps find the version using xpath
>> and
>> then restore it somehow?
>>
>> Help much appreciated.
>>
>>
>> Thanks
>>
>> Harvey
>>
> 
> 
> -- 
> -----------------------------------------< tobias.bocanegra@day.com >---
> Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
> T +41 61 226 98 98, F +41 61 226 98 97
> -----------------------------------------------< http://www.day.com >---
> 
> 

-- 
View this message in context: http://www.nabble.com/Version-Configuration-Confusion-tf3440375.html#a9670138
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Re: Version Configuration Confusion

Posted by Tobias Bocanegra <to...@day.com>.

hi,
if b,c and d have OPV=Version you can do those operations.
to "undelete" a node, you need to know the version you want to restore, and
use the Node.restore(Version version, String relPath, boolean removeExisting)
method. eg: "A".restore("version of B", "B", false);

or you can restore it to a complete different parent, eg:
"someparent".restore("version of B", "newname", false);

regards, toby

On 3/21/07, harvey waters <ha...@googlemail.com> wrote:
> I'm setting up some nodes to do the following...
>
> Node A
> |                |              |
> |                |              |
> Node B      Node C    Node D
>
> Is is possible...
>
> 1) to delete B and then restore Node A (in order to restore B), without
> affecting the state of C
>
> 2)  to delete Node B, then delete Node D, and restore A (to resore Node B)
> but without restoring Node D
>
> Finally, does anyone know if it is possible to un-delete a node without
> having to restore the parent node. Perhaps find the version using xpath and
> then restore it somehow?
>
> Help much appreciated.
>
>
> Thanks
>
> Harvey
>


-- 
-----------------------------------------< tobias.bocanegra@day.com >---
Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97
-----------------------------------------------< http://www.day.com >---

Re: Version Configuration Confusion

Posted by HarveyWaters <ha...@googlemail.com>.

Does anyone know of any documentation regarding the OPV stuff and versioning
in general  (I've tried the JSR 170 but its very confusing and lacks good
real world examples). Yukka should I list this on the development mail list
?



HarveyWaters wrote:
> 
> I'm setting up some nodes to do the following...
> 
> Node A
> |                |              |
> |                |              |
> Node B      Node C    Node D
> 
> Is is possible...
> 
> 1) to delete B and then restore Node A (in order to restore B), without
> affecting the state of C
> 
> 2)  to delete Node B, then delete Node D, and restore A (to resore Node B)
> but without restoring Node D
> 
> Finally, does anyone know if it is possible to un-delete a node without
> having to restore the parent node. Perhaps find the version using xpath
> and
> then restore it somehow?
> 
> Help much appreciated.
> 
> 
> Thanks
> 
> Harvey
> 
> 

-- 
View this message in context: http://www.nabble.com/Version-Configuration-Confusion-tf3440375.html#a9669075
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.