Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (asf.osuosl.org: domain of stefan.guggisberg@gmail.com
 designates 64.233.166.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=DKs050cZuJFXuEQ3Vmb5vl7lZEA3seajBGXPjxCLBxfvDuJbsrgaSB2y0Cvo2WQHB2odzCMlG/W/gU6wHI505lv5SJQ3K4tzzsrggPDt32RssK0I1C5E5tbGpAtRgQhntthvJ47wD7i2rAVnSTXrRz/rO56MEZhOMElq/AuLmkw=
Message-ID: <90a8d1c00608090142l10db223bn30f58760dfcf9c7@mail.gmail.com>
Date: Wed, 9 Aug 2006 10:42:48 +0200
From: "Stefan Guggisberg" <stefan.guggisberg@gmail.com>
To: dev@jackrabbit.apache.org
Subject: Re: Issue when restoring the Node version history
In-Reply-To: <fcbb46050608081121q9f8520aida08cf4c2ca036d4@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <fcbb46050608061159v7a68d6b5le27d7bc0c955f0b8@mail.gmail.com>
	 <8be731880608070200k61e42d6bj14eaba0ec1cac388@mail.gmail.com>
	 <fcbb46050608070223g373ef822qbb4824adf67f38aa@mail.gmail.com>
	 <8be731880608070232m59021793s3a89f01c1fc56434@mail.gmail.com>
	 <fcbb46050608070233u22f482b8o5e5be2bfcee46cd3@mail.gmail.com>
	 <fcbb46050608070234x11d78f45k945a522a03e7bc6f@mail.gmail.com>
	 <fcbb46050608081121q9f8520aida08cf4c2ca036d4@mail.gmail.com>

On 8/8/06, Nicolas <ntoper@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 <ntoper@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 <tobias.bocanegra@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 !!
>
>