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

Posted to dev@jackrabbit.apache.org by Nicolas <nt...@gmail.com> on 2006/08/06 20:59:36 UTC

Issue when restoring the Node version history

Hi,

I have encountered an issue when restoring the node version history. As you
know it is part of the shared subtree /jcr:system. All the versioning is
contained within /jcr:system/jcr:versionStorage. All those nodes are
protected. I have backupped the data by using the exportXML method of
Session.

I encounter a problem to restore it since those node is protected. I have
found quite a few different approach to restore them. I need your feedback
and your ideas on this please to know which one is the best.

1/ Modify temporarily the NodeDefinition of jcr:storage so it is not
protected.
This approach would modify the NodeDefinition of the protected nodes so they
can be unprotected. I would restore the data using import and then restore
the protection and reload the repository. This way seems the easiest to
achieve restore.

2/ Redefine InternalAddChild in NodeImpl so I can bypass protection. This
method is protected. I would need to add a public method in NodeImpl which
would not check any protection. I would then be able to import the data
using importXML.

3/ Add to the VersionManagerImpl a public import method heavily based on the
SessionImpl one. This solution seems the most elegant but might not be the
easiest.

4/ Change the storage format (right now the sysView) in order to get an
easier restore (using for instance Java serialization).

What do you think?

Nico
my blog! http://www.deviant-abstraction.net !!

RE: Issue when restoring the Node version history

Posted by Miro Walker <mi...@cognifide.com>.

Hi Stefan,

Just out of curiosity, under what circumstances could it be useful to
backup/restore the repository without the version storage? If you're
using versionable nodes, then if you lose the version history you end up
in a right old mess. Is there a usage scenario I'm missing here?

miro



-----Original Message-----
From: Stefan Guggisberg [mailto:stefan.guggisberg@gmail.com] 
Sent: 09 August 2006 09:43
To: dev@jackrabbit.apache.org
Subject: Re: Issue when restoring the Node version history

On 8/8/06, Nicolas <nt...@gmail.com> wrote:
> Hi Tobias,
>
> The issue I have is nothing allow
>
> It's really simpler for me to update all protected nodes, restore the
> version history and then switch back to the protection. However to do
so, I
> don't see any other option than adding a method reregisterBuiltIn in
the
> NodeTypeManager... I am not sure if it's a wise decision.

it's not, -1 for reregisterBuiltIn

importXML is not suitable for restoring system managed data.
restoring version data (whether that's a good idea is another question)
should definitely be handled by the VersionManager.

cheers
stefan

> Besides when I
> try  commenting those check, the import is false. I think some
reference are
> out of date...
>
> So unless you have a better idea, I have to implement an importXML
method
> for the Versioning. This method will have to be in core and would
import any
> /jcr:system/jcr:versionStorage of Jackrabbit.
>
> What do you think of this solution? Do you have a better idea?
>
> Nico
>
> On 8/7/06, Nicolas <nt...@gmail.com> wrote:
> >
> >
> >
> > ---------- Forwarded message ----------
> > From: Nicolas < ntoper@gmail.com>
> > Date: Aug 7, 2006 11:33 AM
> > Subject: Re: Issue when restoring the Node version history
> > To: tobias.bocanegra@day.com
> >
> > Yes that's why I thought :)
> >
> > I do think however, adding an import method to the VersionManager is
way
> > more elegant. Do you agree?
> >
> >
> > On 8/7/06, Tobias Bocanegra <to...@day.com> wrote:
> > >
> > > > Why wouldn't it work if we bypass the VersionManager?
> > >
> > > you would need to flush all the caches. but since you probably
restart
> > > the repo anyways after restore, this might not be a problem.
> > >
> > > regards, toby
> > > --
> > > -----------------------------------------<
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 >---
> > >
> >
> >
> >
> > --
> > a+
> >
> > Nico
> > my blog! http://www.deviant-abstraction.net !!
> >
> >
> > --
> > a+
> > Nico
> > my blog! http://www.deviant-abstraction.net !!
> >
>
>
>
> --
> a+
> Nico
> my blog! http://www.deviant-abstraction.net !!
>
>

Re: Issue when restoring the Node version history

Posted by Stefan Guggisberg <st...@gmail.com>.

On 8/8/06, Nicolas <nt...@gmail.com> wrote:
> Hi Tobias,
>
> The issue I have is nothing allow
>
> It's really simpler for me to update all protected nodes, restore the
> version history and then switch back to the protection. However to do so, I
> don't see any other option than adding a method reregisterBuiltIn in the
> NodeTypeManager... I am not sure if it's a wise decision.

it's not, -1 for reregisterBuiltIn

importXML is not suitable for restoring system managed data.
restoring version data (whether that's a good idea is another question)
should definitely be handled by the VersionManager.

cheers
stefan

> Besides when I
> try  commenting those check, the import is false. I think some reference are
> out of date...
>
> So unless you have a better idea, I have to implement an importXML method
> for the Versioning. This method will have to be in core and would import any
> /jcr:system/jcr:versionStorage of Jackrabbit.
>
> What do you think of this solution? Do you have a better idea?
>
> Nico
>
> On 8/7/06, Nicolas <nt...@gmail.com> wrote:
> >
> >
> >
> > ---------- Forwarded message ----------
> > From: Nicolas < ntoper@gmail.com>
> > Date: Aug 7, 2006 11:33 AM
> > Subject: Re: Issue when restoring the Node version history
> > To: tobias.bocanegra@day.com
> >
> > Yes that's why I thought :)
> >
> > I do think however, adding an import method to the VersionManager is way
> > more elegant. Do you agree?
> >
> >
> > On 8/7/06, Tobias Bocanegra <to...@day.com> wrote:
> > >
> > > > Why wouldn't it work if we bypass the VersionManager?
> > >
> > > you would need to flush all the caches. but since you probably restart
> > > the repo anyways after restore, this might not be a problem.
> > >
> > > regards, toby
> > > --
> > > -----------------------------------------< 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 >---
> > >
> >
> >
> >
> > --
> > a+
> >
> > Nico
> > my blog! http://www.deviant-abstraction.net !!
> >
> >
> > --
> > a+
> > Nico
> > my blog! http://www.deviant-abstraction.net !!
> >
>
>
>
> --
> a+
> Nico
> my blog! http://www.deviant-abstraction.net !!
>
>